[
https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061997#comment-13061997
]
Camille Fournier commented on ZOOKEEPER-1054:
---------------------------------------------
It's weird that this patch is against a jira tracker called "Zookeeper logs are
filled with INFO messages", since it isn't about that at all.
Won't this break all that stuff that Alex was talking about at the dev meetup
for his reconfigurable cluster stuff, ZOOKEEPER-107?
> Zookeeper logs are filled with INFO messages
> ---------------------------------------------
>
> 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.4.0
>
> Attachments: ZOOKEEPER-1054-1.patch, ZOOKEEPER-1054-2.patch,
> ZOOKEEPER-1054.patch, zookeeper-1054-3.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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
