[jira] Created: (ZOOKEEPER-788) Add server id to message logs
Add server id to message logs - Key: ZOOKEEPER-788 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-788 Project: Zookeeper Issue Type: Improvement Reporter: Ivan Kelly Assignee: Ivan Kelly Priority: Trivial As discussed on IRC. The log visualisation needs some way of determining which server made which log. If the log segment is taken for a time period where no elections take place, there is no way to determine the id of the server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-788) Add server id to message logs
[ https://issues.apache.org/jira/browse/ZOOKEEPER-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated ZOOKEEPER-788: - Fix Version/s: 3.4.0 Affects Version/s: 3.3.1 Component/s: contrib Add server id to message logs - Key: ZOOKEEPER-788 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-788 Project: Zookeeper Issue Type: Improvement Components: contrib Affects Versions: 3.3.1 Reporter: Ivan Kelly Assignee: Ivan Kelly Priority: Trivial Fix For: 3.4.0 As discussed on IRC. The log visualisation needs some way of determining which server made which log. If the log segment is taken for a time period where no elections take place, there is no way to determine the id of the server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-788) Add server id to message logs
[ https://issues.apache.org/jira/browse/ZOOKEEPER-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated ZOOKEEPER-788: - Status: Patch Available (was: Open) Add server id to message logs - Key: ZOOKEEPER-788 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-788 Project: Zookeeper Issue Type: Improvement Components: contrib Affects Versions: 3.3.1 Reporter: Ivan Kelly Assignee: Ivan Kelly Priority: Trivial Fix For: 3.4.0 Attachments: ZOOKEEPER-778.patch As discussed on IRC. The log visualisation needs some way of determining which server made which log. If the log segment is taken for a time period where no elections take place, there is no way to determine the id of the server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-788) Add server id to message logs
[ https://issues.apache.org/jira/browse/ZOOKEEPER-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated ZOOKEEPER-788: - Attachment: ZOOKEEPER-778.patch Add server id to message logs - Key: ZOOKEEPER-788 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-788 Project: Zookeeper Issue Type: Improvement Components: contrib Affects Versions: 3.3.1 Reporter: Ivan Kelly Assignee: Ivan Kelly Priority: Trivial Fix For: 3.4.0 Attachments: ZOOKEEPER-778.patch As discussed on IRC. The log visualisation needs some way of determining which server made which log. If the log segment is taken for a time period where no elections take place, there is no way to determine the id of the server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-788) Add server id to message logs
[ https://issues.apache.org/jira/browse/ZOOKEEPER-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12879842#action_12879842 ] Hadoop QA commented on ZOOKEEPER-788: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12447362/ZOOKEEPER-778.patch against trunk revision 953041. +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 tests are needed for this patch. -1 patch. The patch command could not apply the patch. Console output: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h7.grid.sp2.yahoo.net/85/console This message is automatically generated. Add server id to message logs - Key: ZOOKEEPER-788 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-788 Project: Zookeeper Issue Type: Improvement Components: contrib Affects Versions: 3.3.1 Reporter: Ivan Kelly Assignee: Ivan Kelly Priority: Trivial Fix For: 3.4.0 Attachments: ZOOKEEPER-778.patch As discussed on IRC. The log visualisation needs some way of determining which server made which log. If the log segment is taken for a time period where no elections take place, there is no way to determine the id of the server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-335) zookeeper servers should commit the new leader txn to their logs.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12879967#action_12879967 ] Mike Solomon commented on ZOOKEEPER-335: I am having this exact issue, but I am not upgrading. I am merely restarting the cluster. I have a cluster of three. I took down host1 and verified that my application remained and reconnected to host2 and host3. With host1 back online, I took down host2. I noticed that the java process was spinning over 100% CPU and realized it had not come back up. This is running the 3.3.0 JAR release on a dual proc, quad-core Intel box. I'm running SuSE 10.3, 64-bit, with this version of java: java version 1.6.0_10 Java(TM) SE Runtime Environment (build 1.6.0_10-b33) Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode) I will attach a log file. zookeeper servers should commit the new leader txn to their logs. - Key: ZOOKEEPER-335 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-335 Project: Zookeeper Issue Type: Bug Components: server Affects Versions: 3.1.0 Reporter: Mahadev konar Assignee: Mahadev konar Priority: Blocker Fix For: 3.4.0 currently the zookeeper followers do not commit the new leader election. This will cause problems in a failure scenarios with a follower acking to the same leader txn id twice, which might be two different intermittent leaders and allowing them to propose two different txn's of the same zxid. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-335) zookeeper servers should commit the new leader txn to their logs.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Solomon updated ZOOKEEPER-335: --- Attachment: zk.log.gz This is the log file of my second attempt to restart a wedged zookeeper server. zookeeper servers should commit the new leader txn to their logs. - Key: ZOOKEEPER-335 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-335 Project: Zookeeper Issue Type: Bug Components: server Affects Versions: 3.1.0 Reporter: Mahadev konar Assignee: Mahadev konar Priority: Blocker Fix For: 3.4.0 Attachments: zk.log.gz currently the zookeeper followers do not commit the new leader election. This will cause problems in a failure scenarios with a follower acking to the same leader txn id twice, which might be two different intermittent leaders and allowing them to propose two different txn's of the same zxid. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-335) zookeeper servers should commit the new leader txn to their logs.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12880001#action_12880001 ] Patrick Hunt commented on ZOOKEEPER-335: Thanks for the log Mike. This issue does seem similar to what Charity reported: 2010-06-17 14:35:34,263 - FATAL [QuorumPeer:/0:0:0:0:0:0:0:0:2181:follo...@71] - Leader epoch 1 is less than our epoch 2 Unfortunately the attached log shows information only after the problem occurred. Any chance you could upload the logs during the initial event? (what I mean is when the problem originally started) Also the logs from the other servers in the ensemble (again, at the time that the problem originally occurred) would really help. Thanks. Have you been able to clear the problem? It's fairly straightforward to resolve - Charity resolved by; 1) bring down the failing server, 2) clear the data directory of that server (only), 3) start that server. You only want to do this for the server that's unable to rejoin the quorum - ie the one thats outputting Leader epoch 1 is less than our epoch 2, _not_ for all servers in the ensemble. zookeeper servers should commit the new leader txn to their logs. - Key: ZOOKEEPER-335 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-335 Project: Zookeeper Issue Type: Bug Components: server Affects Versions: 3.1.0 Reporter: Mahadev konar Assignee: Mahadev konar Priority: Blocker Fix For: 3.4.0 Attachments: zk.log.gz currently the zookeeper followers do not commit the new leader election. This will cause problems in a failure scenarios with a follower acking to the same leader txn id twice, which might be two different intermittent leaders and allowing them to propose two different txn's of the same zxid. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
