You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Norbert Kalmar (JIRA)" <ji...@apache.org> on 2018/06/18 14:45:00 UTC

[jira] [Commented] (ZOOKEEPER-2873) print error and/or abort on invalid server definition

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515801#comment-16515801 ] 

Norbert Kalmar commented on ZOOKEEPER-2873:
-------------------------------------------

Are you still working on this [~mfenes]? 

> 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: Mark Fenes
>            Priority: Minor
>
> 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)