You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Bhallamudi Venkata Siva Kamesh (JIRA)" <ji...@apache.org> on 2011/04/26 10:30:03 UTC
[jira] [Created] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
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
Priority: Minor
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
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025313#comment-13025313 ]
Patrick Hunt commented on ZOOKEEPER-1054:
-----------------------------------------
Seems like in this case we should be printing WARN messages to the log so that the operator can be notified and take action to rectify.
> 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
> Priority: Minor
> Labels: security
>
> 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
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Camille Fournier (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052731#comment-13052731 ]
Hadoop QA commented on ZOOKEEPER-1054:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12480516/ZOOKEEPER-1054-2.patch
against trunk revision 1138100.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/336//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/336//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/336//console
This message is automatically generated.
> 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
>
>
> 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
[jira] [Updated] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Bhallamudi Venkata Siva Kamesh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bhallamudi Venkata Siva Kamesh updated ZOOKEEPER-1054:
------------------------------------------------------
Attachment: ZOOKEEPER-1054-1.patch
> 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.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
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070786#comment-13070786 ]
Mahadev konar commented on ZOOKEEPER-1054:
------------------------------------------
Bhallamudi, do you plan to change the subject for the jira as per Camille's comment?
> 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.5.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
[jira] [Updated] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated ZOOKEEPER-1054:
-------------------------------------
Fix Version/s: (was: 3.4.0)
3.5.0
Moving this out of 3.4 release since its not a blocker.
> 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.5.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
[jira] [Updated] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Bhallamudi Venkata Siva Kamesh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bhallamudi Venkata Siva Kamesh updated ZOOKEEPER-1054:
------------------------------------------------------
Attachment: ZOOKEEPER-1054.patch
> 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
> Priority: Minor
> Labels: security
> Attachments: 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038680#comment-13038680 ]
Hadoop QA commented on ZOOKEEPER-1054:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12480241/ZOOKEEPER-1054-1.patch
against trunk revision 1125581.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/283//testReport/
Findbugs warnings: https://builds.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/283//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/283//console
This message is automatically generated.
> 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.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
[jira] [Updated] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Bh V S Kamesh (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bh V S Kamesh updated ZOOKEEPER-1054:
-------------------------------------
Attachment: zookeeper-1054-4.patch
Hi Patrick,
Thanks for looking into this.
Attaching the same patch building against trunk
> 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: Bh V S Kamesh
> Assignee: Bh V S Kamesh
> Priority: Minor
> Labels: security
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1054-1.patch, ZOOKEEPER-1054-2.patch, ZOOKEEPER-1054.patch, zookeeper-1054-3.patch, zookeeper-1054-4.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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037029#comment-13037029 ]
Hadoop QA commented on ZOOKEEPER-1054:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12479086/ZOOKEEPER-1054.patch
against trunk revision 1125179.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The patch appears to cause tar ant target to fail.
-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/279//testReport/
Console output: https://builds.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/279//console
This message is automatically generated.
> 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.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
[jira] [Updated] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-1054:
------------------------------------
Fix Version/s: 3.4.0
> 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.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
[jira] [Assigned] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt reassigned ZOOKEEPER-1054:
---------------------------------------
Assignee: Bhallamudi Venkata Siva Kamesh
> 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
> Attachments: 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032975#comment-13032975 ]
Hadoop QA commented on ZOOKEEPER-1054:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12479086/ZOOKEEPER-1054.patch
against trunk revision 1099329.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The patch appears to cause tar ant target to fail.
-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/262//testReport/
Console output: https://builds.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/262//console
This message is automatically generated.
> 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
> Priority: Minor
> Labels: security
> Attachments: 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067985#comment-13067985 ]
Patrick Hunt commented on ZOOKEEPER-1054:
-----------------------------------------
Hi Bhallamudi, can you address Camille's comment? ("It's weird that ...") Perhaps update the subject line, description, etc...
> 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
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171661#comment-13171661 ]
Hadoop QA commented on ZOOKEEPER-1054:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12507797/zookeeper-1054-4.patch
against trunk revision 1214571.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/834//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/834//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/834//console
This message is automatically generated.
> 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: Bh V S Kamesh
> Assignee: Bh V S Kamesh
> Priority: Minor
> Labels: security
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1054-1.patch, ZOOKEEPER-1054-2.patch, ZOOKEEPER-1054.patch, zookeeper-1054-3.patch, zookeeper-1054-4.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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Bhallamudi Venkata Siva Kamesh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038572#comment-13038572 ]
Bhallamudi Venkata Siva Kamesh commented on ZOOKEEPER-1054:
-----------------------------------------------------------
I verified the solution by doing manual testing in the following way
1) I am running zookeeper cluster, having following machines
{noformat}
server.1=10.18.52.146:2888:3888
server.2=10.18.52.124:2888:3888
server.3=10.18.52.112:2888:3888
{noformat}
2) Running another zookeeper(203), having following cluster configuration
{noformat}
server.1=10.18.52.203:2888:3888
server.2=10.18.52.146:2888:3888
server.3=10.18.52.118:2888:3888
{noformat}
3) With the above configuration, it is clear that 203 machine tries to connect 146 machine during leader election.As 203 machine is not part of the current cluster configuration,connection request will be ignored by 146 machine and log the following information as warning.
{noformat}
2011-05-23 14:22:35,368 [myid:1] - WARN [/10.18.52.146:3888:QuorumCnxManager$Listener@512] - Received connection request from /10.18.52.203:47553, which is not configured in the zoo.cfg,so, dropping the connection.
{noformat}
> 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.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
[jira] [Updated] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Bhallamudi Venkata Siva Kamesh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bhallamudi Venkata Siva Kamesh updated ZOOKEEPER-1054:
------------------------------------------------------
Attachment: zookeeper-1054-3.patch
> 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
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Bhallamudi Venkata Siva Kamesh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025133#comment-13025133 ]
Bhallamudi Venkata Siva Kamesh commented on ZOOKEEPER-1054:
-----------------------------------------------------------
While accepting connections from other quorum servers, I feel we should validate the client quorum server against configured quorum servers.
> 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
> Priority: Minor
> Labels: security
>
> 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
[jira] [Updated] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Bhallamudi Venkata Siva Kamesh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bhallamudi Venkata Siva Kamesh updated ZOOKEEPER-1054:
------------------------------------------------------
Attachment: ZOOKEEPER-1054-2.patch
> 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
>
>
> 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
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107956#comment-13107956 ]
Hadoop QA commented on ZOOKEEPER-1054:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12485744/zookeeper-1054-3.patch
against trunk revision 1172406.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/563//console
This message is automatically generated.
> 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.5.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
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062007#comment-13062007 ]
Hadoop QA commented on ZOOKEEPER-1054:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12485744/zookeeper-1054-3.patch
against trunk revision 1144087.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/381//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/381//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/381//console
This message is automatically generated.
> 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
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038653#comment-13038653 ]
Hadoop QA commented on ZOOKEEPER-1054:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12480241/ZOOKEEPER-1054-1.patch
against trunk revision 1125581.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/282//testReport/
Findbugs warnings: https://builds.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/282//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/282//console
This message is automatically generated.
> 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.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
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038590#comment-13038590 ]
Hadoop QA commented on ZOOKEEPER-1054:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12480241/ZOOKEEPER-1054-1.patch
against trunk revision 1125581.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/281//testReport/
Findbugs warnings: https://builds.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/281//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/281//console
This message is automatically generated.
> 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.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
[jira] [Commented] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Bhallamudi Venkata Siva Kamesh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065040#comment-13065040 ]
Bhallamudi Venkata Siva Kamesh commented on ZOOKEEPER-1054:
-----------------------------------------------------------
Hi Mahadev,
Last patch (zookeeper-1054-3.patch) submitted by me contain test cases.
> 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
[jira] [Updated] (ZOOKEEPER-1054) Zookeeper logs are filled with
INFO messages
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated ZOOKEEPER-1054:
-------------------------------------
Bhallamudi,
will you be uploading a test case with the patch. We can probably move this to 3.5? What do you think?
> 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