[ https://issues.apache.org/jira/browse/ZOOKEEPER-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622722#action_12622722 ]
Patrick Hunt commented on ZOOKEEPER-111: ---------------------------------------- Flavio, at least one of the tests that's failing (testHammer) seems related to a quorum problem, can you take a look? 2008-08-14 11:28:40,695 - ERROR [FollowerHandler-/127.0.0.1:2599:[EMAIL PROTECTED] - FIXMSG java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.DataInputStream.readInt(DataInputStream.java:370) at org.apache.jute.BinaryInputArchive.readInt(BinaryInputArchive.java:64) at org.apache.zookeeper.server.quorum.QuorumPacket.deserialize(QuorumPacket.java:65) at org.apache.jute.BinaryInputArchive.readRecord(BinaryInputArchive.java:109) at org.apache.zookeeper.server.quorum.FollowerHandler.run(FollowerHandler.java:279) After which the followers all seem to shutdown. The test is failing because the clients are not complete (10 clients creating 1000 nodes) even after 5 minutes. What type of hardware is this? > significant cleanup of existing tests > ------------------------------------- > > Key: ZOOKEEPER-111 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-111 > Project: Zookeeper > Issue Type: Improvement > Components: tests > Reporter: Patrick Hunt > Assignee: Patrick Hunt > Attachments: TEST-org.apache.zookeeper.test.AsyncTest.txt, > TEST-org.apache.zookeeper.test.QuorumTest.txt, ZOOKEEPER-111.patch, > ZOOKEEPER-111.patch, ZOOKEEPER-111.patch, ZOOKEEPER-111.patch, > ZOOKEEPER-111.patch > > > About to submit a patch that significantly cleans up existing tests. > 1) removed the need for "sleep" calls in the tests, instead I monitor the > status of the server (using the client socket "stat" command) which provides > a barrier to the client test operations. I use this barrier both when > starting and ending the test. > 2) also fixed a number of problems in the tests where the test itself was > broken. > 3) general cleanup and some refactoring to make it easier to write new tests, > maintain old, and track down issues if the test does find a problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.