[
https://issues.apache.org/jira/browse/HBASE-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418936#comment-13418936
]
Lars Hofhansl commented on HBASE-6406:
--------------------------------------
TestZooKeeper.testClientSessionExpired failed again in latest 0.94 build.
Although this is not obvious from the logs the pattern in the code is that same
as in TestReplicationPeer.
My initial suspicion was RecoverableZooKeeper and that it somehow retries the
operation and thereby reconnects the expired session. According to the code it
does not do that, though.
Somehow HBaseTestingUtil.expireSession is subject to racing.
In the case of TestReplicationPeer that happened when expireSession is called
before the connection was actually established.
Is there a way to check whether the connection was established first and wait
if it wasn't?
Otherwise, I'd say we disable this test for now.
> TestReplicationPeer.testResetZooKeeperSession and
> TestZooKeeper.testClientSessionExpired fail frequently
> --------------------------------------------------------------------------------------------------------
>
> Key: HBASE-6406
> URL: https://issues.apache.org/jira/browse/HBASE-6406
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.1
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 0.96.0, 0.94.1
>
> Attachments: 6406.txt, testReplication.jstack, testZooKeeper.jstack
>
>
> Looking back through the 0.94 test runs these two tests accounted for 11 of
> 34 failed tests.
> They should be fixed or (temporarily) disabled.
--
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
