You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Enrico Olivelli (Jira)" <ji...@apache.org> on 2019/09/06 15:44:02 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 ]
Enrico Olivelli updated ZOOKEEPER-934:
--------------------------------------
Fix Version/s: 3.5.7
> 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
> Priority: Major
> Fix For: 3.6.0, 3.5.6, 3.5.7
>
>
> 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
(v8.3.2#803003)