[
https://issues.apache.org/jira/browse/HBASE-6354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409104#comment-13409104
]
Himanshu Vashishtha commented on HBASE-6354:
--------------------------------------------
Changes done in the second patch. It always passes when ran in junit in
eclipse, but it failed (and timed out) when running as mvn test. jstack shows
the thread running the test suite (Surefire) waits (TIMED_WAITING) on the
atomic boolean object (which makes sense as zookeeper didn't invoke the process
method on the watcher); the only other thread that waits (timed_waiting) was
SessionTracker (instance of SessionTrackerImpl) at the following code,
{code}
if (nextExpirationTime > currentTime) {
this.wait(nextExpirationTime - currentTime);
continue;
}
{code}
This does a timed wait, so, it shouldn't cause the test to timed out (i.e.,
block this thread for 5 minutes when the default tick time is 5 seconds). I
find the thread blocking on the same condition even after 2 minutes. Still
looking into it.
What is the difference between mvn environment and eclipse environment (when we
run the junit test). I am using 3.4.3 jar in eclipse environment.
> Wait till hard fail in case of erratic zookeeper session expiry
> ---------------------------------------------------------------
>
> Key: HBASE-6354
> URL: https://issues.apache.org/jira/browse/HBASE-6354
> Project: HBase
> Issue Type: Improvement
> Reporter: Himanshu Vashishtha
> Attachments: HBase6354-v1.patch
>
>
> There are number of tests that depends on zookeeper expire session
> (HBaseTestingUtility#expireSession). The current approach is to create
> handles on the existing sessions and call a close() on one of the handle. It
> closes all the handles associated with this session. This should work in
> theory but sometimes, it just doesn't work (don't know the root cause yet).
> We need to do some hacks ( such as in TestZookeeper#testClientSessionExpired).
--
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
