Hudson build is back to normal: ZooKeeper-trunk #354
See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/354/
[jira] Commented: (ZOOKEEPER-408) address all findbugs warnings in persistence classes
[ https://issues.apache.org/jira/browse/ZOOKEEPER-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722555#action_12722555 ] Hudson commented on ZOOKEEPER-408: -- Integrated in ZooKeeper-trunk #354 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/354/]) > address all findbugs warnings in persistence classes > > > Key: ZOOKEEPER-408 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-408 > Project: Zookeeper > Issue Type: Sub-task >Reporter: Patrick Hunt >Assignee: Mahadev konar > Fix For: 3.2.0 > > Attachments: ZOOKEEPER-408.patch, ZOOKEEPER-408.patch, > ZOOKEEPER-408.patch, ZOOKEEPER-408.patch, ZOOKEEPER-408.patch, > ZOOKEEPER-408.patch > > > trunk/src/java/main/org/apache/zookeeper/server/DataTree.java > trunk/src/java/main/org/apache/zookeeper/server/persistence/FileTxnSnapLog.java > trunk/src/java/main/org/apache/zookeeper/server/persistence/FileTxnLog.java > trunk/src/java/main/org/apache/zookeeper/server/persistence/Util.java > trunk/src/java/main/org/apache/zookeeper/server/DataNode.java > trunk/src/java/main/org/apache/zookeeper/server/upgrade/DataNodeV1.java > trunk/src/java/main/org/apache/zookeeper/server/upgrade/DataTreeV1.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-422) Java CLI should support ephemeral and sequential node creation
[ https://issues.apache.org/jira/browse/ZOOKEEPER-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722553#action_12722553 ] Hudson commented on ZOOKEEPER-422: -- Integrated in ZooKeeper-trunk #354 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/354/]) > Java CLI should support ephemeral and sequential node creation > -- > > Key: ZOOKEEPER-422 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-422 > Project: Zookeeper > Issue Type: Improvement >Affects Versions: 3.2.0 >Reporter: Henry Robinson >Assignee: Henry Robinson >Priority: Minor > Fix For: 3.2.0 > > Attachments: ZOOKEEPER-422.patch > > > The C client supports creation of ephemeral and sequential nodes. For feature > parity, so should the Java CLI. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-427) ZooKeeper server unexpectedly high CPU utilisation
[ https://issues.apache.org/jira/browse/ZOOKEEPER-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722554#action_12722554 ] Hudson commented on ZOOKEEPER-427: -- Integrated in ZooKeeper-trunk #354 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/354/]) > ZooKeeper server unexpectedly high CPU utilisation > -- > > Key: ZOOKEEPER-427 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-427 > Project: Zookeeper > Issue Type: Bug >Affects Versions: 3.1.1 > Environment: Linux: 2.6.18-92.1.18.el5 #1 SMP Wed Nov 12 09:19:49 EST > 2008 x86_64 x86_64 x86_64 GNU/Linux > java version "1.6.0_03" > Java(TM) SE Runtime Environment (build 1.6.0_03-b05) > Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-b05, mixed mode) >Reporter: Satish Bhatti >Assignee: Flavio Paiva Junqueira >Priority: Blocker > Fix For: 3.2.0 > > Attachments: zk_quorum_recv_eof.patch, zoo.cfg, ZOOKEEPER-427.patch, > zookeeper-jstack.log, zookeeper.log > > > I am running a 5 node ZooKeeper cluster and I noticed that one of them has > very high CPU usage: > PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND > 6883 infact 22 0 725m 41m 4188 S 95 0.5 > 5671:54 java > It is not "doing anything" application-wise at this point, so I was wondering > why the heck it's using up so much CPU. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-315) add forrest docs for bookkeeper.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Paiva Junqueira updated ZOOKEEPER-315: - Attachment: ZOOKEEPER-315.patch > add forrest docs for bookkeeper. > > > Key: ZOOKEEPER-315 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-315 > Project: Zookeeper > Issue Type: Improvement > Components: contrib-bookkeeper >Affects Versions: 3.1.0 >Reporter: Mahadev konar >Assignee: Flavio Paiva Junqueira >Priority: Blocker > Fix For: 3.2.0 > > Attachments: ZOOKEEPER-315.patch, ZOOKEEPER-315.patch, > ZOOKEEPER-315.patch > > > we should have forrest docs for bookkeeper for > - how to install bookkeeper > - usage model > - programming examples for users > - FAQ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-315) add forrest docs for bookkeeper.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Paiva Junqueira updated ZOOKEEPER-315: - Status: Patch Available (was: Open) > add forrest docs for bookkeeper. > > > Key: ZOOKEEPER-315 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-315 > Project: Zookeeper > Issue Type: Improvement > Components: contrib-bookkeeper >Affects Versions: 3.1.0 >Reporter: Mahadev konar >Assignee: Flavio Paiva Junqueira >Priority: Blocker > Fix For: 3.2.0 > > Attachments: ZOOKEEPER-315.patch, ZOOKEEPER-315.patch, > ZOOKEEPER-315.patch > > > we should have forrest docs for bookkeeper for > - how to install bookkeeper > - usage model > - programming examples for users > - FAQ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-237) Add a Chroot request
[ https://issues.apache.org/jira/browse/ZOOKEEPER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-237: Status: Patch Available (was: Open) > Add a Chroot request > > > Key: ZOOKEEPER-237 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-237 > Project: Zookeeper > Issue Type: New Feature > Components: c client, java client >Reporter: Benjamin Reed >Assignee: Mahadev konar >Priority: Minor > Fix For: 3.2.0 > > Attachments: ZOOKEEPER-237.patch, ZOOKEEPER-237.patch, > ZOOKEEPER-237.patch > > > It would be nice to be able to root ZooKeeper handles at specific points in > the namespace, so that applications that use ZooKeeper can work in their own > rooted subtree. > For example, if ops decides that application X can use the subtree /apps/X > and application Y can use the subtree /apps/Y, X can to a chroot to /apps/X > and then all its path references can be rooted at /apps/X. Thus when X > creates the path "/myid", it will actually be creating the path > "/apps/X/myid". > There are two ways we can expose this mechanism: 1) We can simply add a > chroot(String path) API, or 2) we can integrate into a service identifier > scheme for example zk://server1:2181,server2:2181/my/root. I like the second > form personally. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-237) Add a Chroot request
[ https://issues.apache.org/jira/browse/ZOOKEEPER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-237: Attachment: ZOOKEEPER-237.patch This patch implements the c and includes the java part as well. It has unit tests for watcher testings/and all the apis testing with chroot enabled. > Add a Chroot request > > > Key: ZOOKEEPER-237 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-237 > Project: Zookeeper > Issue Type: New Feature > Components: c client, java client >Reporter: Benjamin Reed >Assignee: Mahadev konar >Priority: Minor > Fix For: 3.2.0 > > Attachments: ZOOKEEPER-237.patch, ZOOKEEPER-237.patch, > ZOOKEEPER-237.patch > > > It would be nice to be able to root ZooKeeper handles at specific points in > the namespace, so that applications that use ZooKeeper can work in their own > rooted subtree. > For example, if ops decides that application X can use the subtree /apps/X > and application Y can use the subtree /apps/Y, X can to a chroot to /apps/X > and then all its path references can be rooted at /apps/X. Thus when X > creates the path "/myid", it will actually be creating the path > "/apps/X/myid". > There are two ways we can expose this mechanism: 1) We can simply add a > chroot(String path) API, or 2) we can integrate into a service identifier > scheme for example zk://server1:2181,server2:2181/my/root. I like the second > form personally. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-446) some traces of the host auth scheme left
[ https://issues.apache.org/jira/browse/ZOOKEEPER-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar reassigned ZOOKEEPER-446: --- Assignee: Benjamin Reed > some traces of the host auth scheme left > > > Key: ZOOKEEPER-446 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-446 > Project: Zookeeper > Issue Type: Bug >Reporter: Benjamin Reed >Assignee: Benjamin Reed > Fix For: 3.2.0 > > Attachments: ZOOKEEPER-446.patch > > > the host auth scheme was removed because it used a blocking call in an async > pipeline. however, tragically, the blocking call was not removed including a > couple of other stray classes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-446) some traces of the host auth scheme left
[ https://issues.apache.org/jira/browse/ZOOKEEPER-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-446: Resolution: Fixed Status: Resolved (was: Patch Available) +1 ... excellent patch ben :)... just a note : - for files you want to delete, mention it on the jira that run svn delete for that file. svn diff and patch will create an empty file and the empty file stays there. I have committed this. thanks ben... > some traces of the host auth scheme left > > > Key: ZOOKEEPER-446 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-446 > Project: Zookeeper > Issue Type: Bug >Reporter: Benjamin Reed >Assignee: Benjamin Reed > Fix For: 3.2.0 > > Attachments: ZOOKEEPER-446.patch > > > the host auth scheme was removed because it used a blocking call in an async > pipeline. however, tragically, the blocking call was not removed including a > couple of other stray classes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.2.0 to a Maven Repository
[ https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722951#action_12722951 ] Giridharan Kesavan commented on ZOOKEEPER-224: -- I'm working on getting the hadoop jars published to the maven repository using ivy. In the case of zookeeper as well we can use ivy to publish zookeeper.jar. > Deploy ZooKeeper 3.2.0 to a Maven Repository > > > Key: ZOOKEEPER-224 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-224 > Project: Zookeeper > Issue Type: Task > Components: build >Affects Versions: 3.0.0 >Reporter: Hiram Chirino >Assignee: Patrick Hunt >Priority: Critical > Fix For: 3.2.0 > > > I've created the maven poms needed for the 3.0.0 release. > The directory structure and artifacts located at: > http://people.apache.org/~chirino/zk-repo/ > aka > people.apache.org:/x1/users/chirino/public_html/zk-repo > Just need sto get GPG signed by the project KEY and deployed to: > people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository > Who's the current ZooKeeper release manager? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
