zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Norbert Kalmar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-2873) print error and/or abort on invalid server definition
Date Mon, 09 Jul 2018 09:23:00 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Norbert Kalmar updated ZOOKEEPER-2873:
--------------------------------------
    Fix Version/s:     (was: 3.6.0)
                   3.4.13

> print error and/or abort on invalid server definition
> -----------------------------------------------------
>
>                 Key: ZOOKEEPER-2873
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2873
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.4.10
>            Reporter: Christopher Smith
>            Assignee: Norbert Kalmar
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.4.13, 3.5.5
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> While bringing up a new cluster, I managed to fat-finger a sed script and put some lines
like this into my config file:
> {code}
> server.1=zookeeper1:2888:2888
> {code}
> This led to a predictable spew of error messages when the client and election components
fought over the single port. Since a configuration of this case is *always* an error, I suggest
that it would be sensible to abort the server startup if an entry is found with the same port
for both client and election. (Logging the error explicitly without shutting down is less
helpful because of how fast the logs pile up.)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message