You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2017/03/13 16:22:10 UTC

[jira] [Updated] (ZOOKEEPER-934) Add sanity check for server ID

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

Michael Han updated ZOOKEEPER-934:
----------------------------------
    Fix Version/s:     (was: 3.5.3)
                   3.5.4

> Add sanity check for server ID
> ------------------------------
>
>                 Key: ZOOKEEPER-934
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-934
>             Project: ZooKeeper
>          Issue Type: Sub-task
>            Reporter: Vishal Kher
>             Fix For: 3.5.4, 3.6.0
>
>
> 2. Should I add a check to reject connections from peers that are not
> listed in the configuration file? Currently, we are not doing any
> sanity check for server IDs. I think this might fix ZOOKEEPER-851.
> The fix is simple. However, I am not sure if anyone in community
> is relying on this ability.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)