[jira] Updated: (ZOOKEEPER-204) SetWatches needs to be the first message after auth messages to the server
[ https://issues.apache.org/jira/browse/ZOOKEEPER-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-204: --- Fix Version/s: 3.0.1 > SetWatches needs to be the first message after auth messages to the server > -- > > Key: ZOOKEEPER-204 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-204 > Project: Zookeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.0.0 >Reporter: Benjamin Reed >Assignee: Benjamin Reed > Fix For: 3.0.1, 3.1.0 > > Attachments: ZOOKEEPER-204.patch, ZOOKEEPER-204.patch > > > When the ZooKeeper java client makes a connection it queues a SetWatches > request. The problem is that it puts the request at the end of the outgoing > requests. This means that watches for requests that were queued before the > connection is made and after the disconnect may improperly get their watches > triggered. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-212) snapshot is synchronous in 3.0
[ https://issues.apache.org/jira/browse/ZOOKEEPER-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-212: --- Fix Version/s: 3.0.1 > snapshot is synchronous in 3.0 > -- > > Key: ZOOKEEPER-212 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-212 > Project: Zookeeper > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Mahadev konar >Assignee: Mahadev konar >Priority: Critical > Fix For: 3.0.1, 3.1.0 > > Attachments: ZOOKEEPER-212-test.patch, ZOOKEEPER-212.patch > > > the snapshot in 3.0 is syunchronous. this will affect performance of the > system. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-211) Not all Mock tests are working
[ https://issues.apache.org/jira/browse/ZOOKEEPER-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-211: --- Fix Version/s: 3.1.0 3.0.1 > Not all Mock tests are working > -- > > Key: ZOOKEEPER-211 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-211 > Project: Zookeeper > Issue Type: Test > Components: c client >Reporter: Benjamin Reed >Assignee: Benjamin Reed >Priority: Minor > Fix For: 3.0.1, 3.1.0 > > Attachments: ZOOKEEPER-211.patch > > > For the 3.0 release there was a bug in the ZKMock code that prevented some > tests from working. This patch fixes the bug and reenables the tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-135) Fat jar build target
[ https://issues.apache.org/jira/browse/ZOOKEEPER-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-135: --- Fix Version/s: 3.1.0 ben let's try to get an updated patch into 3.1? > Fat jar build target > > > Key: ZOOKEEPER-135 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-135 > Project: Zookeeper > Issue Type: New Feature > Components: build >Reporter: Benjamin Reed >Assignee: Benjamin Reed >Priority: Minor > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-135.patch > > > For testing and experimentation purposes it would be nice to have everything > in a self contained executable jar file that you can plop down on a machine > and run. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-177) needed: docs for JMX
[ https://issues.apache.org/jira/browse/ZOOKEEPER-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645125#action_12645125 ] Patrick Hunt commented on ZOOKEEPER-177: One thing I noticed when running jmx on my linux system with jdk6 If you start ManagedQuorumPeerMain (3.x) with this option: -J-Djava.rmi.server.hostname=localhost you can use jconsole to attach on localhost. otw you get some weird error related to the jvm host name not matching (something like that) > needed: docs for JMX > > > Key: ZOOKEEPER-177 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-177 > Project: Zookeeper > Issue Type: Improvement > Components: documentation, jmx >Reporter: Robbie Scott > Fix For: 3.1.0 > > > I don't know if this should be part of the logging section in the zookeeper > admin guide (see JIRA ZOOKEEPER-166 ) > but, per Patrick, "related to security, ack, yea another doc, is the > documentation of the JMX support that zk has" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-177) needed: docs for JMX
[ https://issues.apache.org/jira/browse/ZOOKEEPER-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-177: --- Fix Version/s: 3.1.0 > needed: docs for JMX > > > Key: ZOOKEEPER-177 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-177 > Project: Zookeeper > Issue Type: Improvement > Components: documentation, jmx >Reporter: Robbie Scott > Fix For: 3.1.0 > > > I don't know if this should be part of the logging section in the zookeeper > admin guide (see JIRA ZOOKEEPER-166 ) > but, per Patrick, "related to security, ack, yea another doc, is the > documentation of the JMX support that zk has" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-216) Improve logging in C client
Improve logging in C client --- Key: ZOOKEEPER-216 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-216 Project: Zookeeper Issue Type: Improvement Components: c client Affects Versions: 3.0.0 Reporter: Patrick Hunt Fix For: 3.1.0 While debugging a client issue we saw multiple areas for improvement in C logging. It might be a good idea to also move to log4c. Anyone have experience with this? multithread an issue? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-215) expand system test environment
expand system test environment -- Key: ZOOKEEPER-215 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-215 Project: Zookeeper Issue Type: New Feature Components: tests Reporter: Patrick Hunt Assignee: Benjamin Reed Fix For: 3.1.0 Currently our system tests are lumped in with our unit tests. It would be great to have a system test environment where we could run larger scale testing. Say you have 20 hosts, and you would like to test a serving ensemble with 7 servers and 100 clients running particular operations. It should be easy to test this scenario. Additionally during the test it should be possible to simulate serving node failure, etc... I've had a brief conversation with Ben about this and he's going to take this JIRA. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-214) add new "stat reset" command to server admin port
add new "stat reset" command to server admin port - Key: ZOOKEEPER-214 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-214 Project: Zookeeper Issue Type: Improvement Components: server Reporter: Patrick Hunt Fix For: 3.1.0 A new command should be added to the server admin port (client port) that allows users to reset the stats. We saw cases during troubleshooting where we would have liked to reset the "min/avg/max latency" stats, but were unable to do so (short of restarting the server). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Hudson build is back to normal: ZooKeeper-trunk #133
See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/133/changes
