[
https://issues.apache.org/jira/browse/ZOOKEEPER-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated ZOOKEEPER-1271:
-------------------------------------
Attachment: ZOOKEEPER-1271-3.3.patch
Patch for 3.3 branch. The code base in 3.3 makes it almost impossible to write
a unit test for this. We can just commit the patch for 3.3 branch? Lesser
chances of fix getting removed in 3.3. We can just run the patch on solaris
machine and see if it works. Sounds good?
> testEarlyLeaderAbandonment failing on solaris - clients not retrying
> connection
> -------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1271
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1271
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.3.4, 3.4.0, 3.5.0
> Reporter: Patrick Hunt
> Assignee: Mahadev konar
> Priority: Blocker
> Fix For: 3.3.4, 3.4.0, 3.5.0
>
> Attachments: ZOOKEEPER-1271-3.3.patch, ZOOKEEPER-1271-3.4.patch,
> ZOOKEEPER-1271-trunk.patch, ZOOKEEPER-1271.patch, ZOOKEEPER-1271.patch,
> solarisClientFailure.txt.gz
>
>
> See:
> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper_branch34_solaris/1/testReport/junit/org.apache.zookeeper.server.quorum/QuorumPeerMainTest/testEarlyLeaderAbandonment/
> Notice that the clients attempt to connect before the servers have bound,
> then 30 seconds later, after seemingly no further client activity we see:
> 2011-10-28 21:40:56,828 [myid:] - INFO
> [main-SendThread(localhost:11227):ClientCnxn$SendThread@1057] - Client
> session timed out, have not heard from server in 30032ms for sessionid 0x0,
> closing socket connection and attempting reconnect
> I believe this is different from ZOOKEEPER-1270 because in the 1270 case it
> seems like the clients are attempting to connect but the servers are not
> accepting (notice the stat commands are being dropped due to no server
> running)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
