[jira] Updated: (ZOOKEEPER-205) Error on version-info when compiling from the tarball distribution
[
https://issues.apache.org/jira/browse/ZOOKEEPER-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flavio Paiva Junqueira updated ZOOKEEPER-205:
-
Summary: Error on version-info when compiling from the tarball distribution
(was: Erro on version-info when compiling from the tarball distribution)
Error on version-info when compiling from the tarball distribution
--
Key: ZOOKEEPER-205
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-205
Project: Zookeeper
Issue Type: Bug
Affects Versions: 3.1.0
Reporter: Flavio Paiva Junqueira
Priority: Minor
Fix For: 3.0.0
When running ant with the code from the release tarball, I get the following
messages and stack trace:
{noformat}
svn-revision:
[exec] svn: '.' is not a working copy
version-info:
[java] All version-related parameters must be valid integers!
[java] Exception in thread main java.lang.NumberFormatException: For
input string:
[java] at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
[java] at java.lang.Integer.parseInt(Integer.java:468)
[java] at java.lang.Integer.parseInt(Integer.java:497)
[java] at
org.apache.zookeeper.version.util.VerGen.main(VerGen.java:111)
[java] Java Result: 1
{noformat}
This seems to be because the code is not coming from svn, so it can't find
the version information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: [VOTE] Release ZooKeeper 3.0.0 (candidate 0)
+1 -Flavio -Original Message- From: Mahadev Konar [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 22, 2008 9:11 PM To: zookeeper-dev@hadoop.apache.org Subject: Re: [VOTE] Release ZooKeeper 3.0.0 (candidate 0) +1 mahadev On 10/22/08 8:59 AM, Benjamin Reed [EMAIL PROTECTED] wrote: +1 -Original Message- From: Patrick Hunt [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 11:29 PM To: zookeeper-dev@hadoop.apache.org Subject: [VOTE] Release ZooKeeper 3.0.0 (candidate 0) I've created a candidate build for the first Apache release of ZooKeeper - version 3.0.0. *** Please download, test and VOTE before the *** vote closes EOD on Friday, October 24.*** http://people.apache.org/~phunt/zookeeper-3.0.0-candidate-0/ Patrick
Re: [VOTE] Release ZooKeeper 3.0.0 (candidate 0)
+1. Very nice job for a first release of *Apache* ZooKeeper! Nige On Oct 21, 2008, at 11:29 PM, Patrick Hunt wrote: I've created a candidate build for the first Apache release of ZooKeeper - version 3.0.0. *** Please download, test and VOTE before the *** vote closes EOD on Friday, October 24.*** http://people.apache.org/~phunt/zookeeper-3.0.0-candidate-0/ Patrick
Re: [VOTE] Release ZooKeeper 3.0.0 (candidate 0)
+1 The release looks great, much better than most first releases! I noticed a few minor problems in the documentation, but these should by no means not stop the release. In particular: - The Zookeeper Documentation tab should contain the version number. - Informal Documentation might better be named Other Documentation. - The Other Info page should be removed, since it contains nothing. - a logo (ZOOKEEPER-69), any logo, would sure be nice. Doug Patrick Hunt wrote: I've created a candidate build for the first Apache release of ZooKeeper - version 3.0.0. *** Please download, test and VOTE before the *** vote closes EOD on Friday, October 24.*** http://people.apache.org/~phunt/zookeeper-3.0.0-candidate-0/ Patrick
Re: [VOTE] Release ZooKeeper 3.0.0 (candidate 0)
Thanks for the feedback Doug. 1) I created ZOOKEEPER-206 to address the first 3 issues you mentioned 2) regarding the logo this is already captured at ZOOKEEPER-69. We have a preliminary logo, working to finalize (should be soon) Patrick Doug Cutting wrote: +1 The release looks great, much better than most first releases! I noticed a few minor problems in the documentation, but these should by no means not stop the release. In particular: - The Zookeeper Documentation tab should contain the version number. - Informal Documentation might better be named Other Documentation. - The Other Info page should be removed, since it contains nothing. - a logo (ZOOKEEPER-69), any logo, would sure be nice. Doug Patrick Hunt wrote: I've created a candidate build for the first Apache release of ZooKeeper - version 3.0.0. *** Please download, test and VOTE before the *** vote closes EOD on Friday, October 24.*** http://people.apache.org/~phunt/zookeeper-3.0.0-candidate-0/ Patrick
[jira] Updated: (ZOOKEEPER-69) ZooKeeper logo
[ https://issues.apache.org/jira/browse/ZOOKEEPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-69: -- Fix Version/s: 3.1.0 Assignee: Benjamin Reed Reassigning to Ben for 3.1.0. I believe he has something in the works. ZooKeeper logo -- Key: ZOOKEEPER-69 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-69 Project: Zookeeper Issue Type: Wish Components: documentation Reporter: Flavio Paiva Junqueira Assignee: Benjamin Reed Priority: Minor Fix For: 3.1.0 I think we need a cool logo for the project. The ones I've seen so far are a little lame, and that includes the one I've created for SourceForge. If anyone on this list has an idea or knows of anyone with some art skills, plese add a commento to this Jira. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-205) Error on version-info when compiling from the tarball distribution
[
https://issues.apache.org/jira/browse/ZOOKEEPER-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12642333#action_12642333
]
Mahadev konar commented on ZOOKEEPER-205:
-
yes, the script should just return 0.0.0 in case it fails to do svn revision...
Error on version-info when compiling from the tarball distribution
--
Key: ZOOKEEPER-205
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-205
Project: Zookeeper
Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Flavio Paiva Junqueira
Priority: Minor
Fix For: 3.1.0
When running ant with the code from the release tarball, I get the following
messages and stack trace:
{noformat}
svn-revision:
[exec] svn: '.' is not a working copy
version-info:
[java] All version-related parameters must be valid integers!
[java] Exception in thread main java.lang.NumberFormatException: For
input string:
[java] at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
[java] at java.lang.Integer.parseInt(Integer.java:468)
[java] at java.lang.Integer.parseInt(Integer.java:497)
[java] at
org.apache.zookeeper.version.util.VerGen.main(VerGen.java:111)
[java] Java Result: 1
{noformat}
This seems to be because the code is not coming from svn, so it can't find
the version information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-126) zookeeper client close operation may block indefinitely
[ https://issues.apache.org/jira/browse/ZOOKEEPER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12642338#action_12642338 ] Mahadev konar commented on ZOOKEEPER-126: - was this problem fixed with fixes to the client code in 3.0? zookeeper client close operation may block indefinitely --- Key: ZOOKEEPER-126 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-126 Project: Zookeeper Issue Type: Bug Components: java client Reporter: Patrick Hunt Attachments: ZOOKEEPER-126.patch Moving the hang issue from ZOOKEEPER-63 to here. See 63 for background and potential patch (patch_ZOOKEEPER-63.patch). specifically (from James): I'm thinking the close() method should not wait() forever on the disconnect packet, just a closeTimeout length - say a few seconds. Afterall blocking and forcing a reconnect just to redeliver the disconnect packet seems a bit silly - when the server has to deal with clients which just have their sockets fail anyway -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-158) Leader and followers increase cpu utilization upon loss of a follower
[ https://issues.apache.org/jira/browse/ZOOKEEPER-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12642340#action_12642340 ] Mahadev konar commented on ZOOKEEPER-158: - well if its easy to reproduce then we should be able to just attach a profiler to the nodes i will try this out with a profiler and post the results ... Leader and followers increase cpu utilization upon loss of a follower - Key: ZOOKEEPER-158 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-158 Project: Zookeeper Issue Type: Improvement Components: quorum Reporter: Flavio Paiva Junqueira Assignee: Mahadev konar Priority: Minor Attachments: dead-follower.tar.gz In a set of ZooKeeper servers, when there is a leader operation and supported by a quorum of servers, we have observed that cpu utilization increases substantially once a follower fails or disconnects. Stu Hood provided logs showing this behavior. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-158) Leader and followers increase cpu utilization upon loss of a follower
[ https://issues.apache.org/jira/browse/ZOOKEEPER-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12642345#action_12642345 ] Flavio Paiva Junqueira commented on ZOOKEEPER-158: -- I think that profiling is a great idea in this case. Leader and followers increase cpu utilization upon loss of a follower - Key: ZOOKEEPER-158 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-158 Project: Zookeeper Issue Type: Improvement Components: quorum Reporter: Flavio Paiva Junqueira Assignee: Mahadev konar Priority: Minor Attachments: dead-follower.tar.gz In a set of ZooKeeper servers, when there is a leader operation and supported by a quorum of servers, we have observed that cpu utilization increases substantially once a follower fails or disconnects. Stu Hood provided logs showing this behavior. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-158) Leader and followers increase cpu utilization upon loss of a follower
[ https://issues.apache.org/jira/browse/ZOOKEEPER-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12642346#action_12642346 ] Patrick Hunt commented on ZOOKEEPER-158: another interesting thing to try is run with JMX enabled and you can use jconsole to attach to the VM and get some detail about the VM/ZK during the election. Leader and followers increase cpu utilization upon loss of a follower - Key: ZOOKEEPER-158 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-158 Project: Zookeeper Issue Type: Improvement Components: quorum Reporter: Flavio Paiva Junqueira Assignee: Mahadev konar Priority: Minor Attachments: dead-follower.tar.gz In a set of ZooKeeper servers, when there is a leader operation and supported by a quorum of servers, we have observed that cpu utilization increases substantially once a follower fails or disconnects. Stu Hood provided logs showing this behavior. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
