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:03 UTC

[jira] [Updated] (ZOOKEEPER-1054) Drop connections from servers not in the cluster configuration

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

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

> Drop connections from servers not in the cluster configuration
> --------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1054
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1054
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: leaderElection
>            Reporter: Bhallamudi Venkata Siva Kamesh
>            Assignee: Bhallamudi Venkata Siva Kamesh
>            Priority: Minor
>              Labels: security
>             Fix For: 3.5.4, 3.6.0
>
>         Attachments: ZOOKEEPER-1054-1.patch, ZOOKEEPER-1054-2.patch, zookeeper-1054-3.patch, zookeeper-1054-4.patch, ZOOKEEPER-1054.patch
>
>
> Let us suppose zookeeper cluster is running in the following machines
> {noformat}
> server.1=10.18.52.133:2999:3999
> server.2=10.18.52.253:2999:3999
> server.3=10.18.52.96:2999:3999
> {noformat}
> Let us take another zookeeper(10.18.52.109),which is not part of the cluster configuration, tries to participate in the leader election,then one of the zookeeper server's log is filled with following INFO messages
> {noformat}
> 2011-04-19 17:42:42,457 - INFO  [/10.18.52.133:3999:QuorumCnxManager$Listener@486] - Received connection request /10.18.52.109:18324
> {noformat}



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