You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2014/11/26 21:56:15 UTC
[jira] [Commented] (HBASE-12587)
TestReplicationTrackerZKImpl.testPeerRemovedEvent timedout
[ https://issues.apache.org/jira/browse/HBASE-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226806#comment-14226806 ]
stack commented on HBASE-12587:
-------------------------------
Pushed to branch-1+ Will leave open in case doesn't fix.
On why this is happening now, I cannot say. This code looks like it should be undisturbed by all the churn in connection setup since this is all about zk watcher's in essence.
> TestReplicationTrackerZKImpl.testPeerRemovedEvent timedout
> ----------------------------------------------------------
>
> Key: HBASE-12587
> URL: https://issues.apache.org/jira/browse/HBASE-12587
> Project: HBase
> Issue Type: Task
> Components: test
> Reporter: stack
> Attachments: 12587.txt
>
>
> Test timedout in branch-1: https://builds.apache.org/view/H-L/view/HBase/job/HBase-1.0/508/testReport/junit/org.apache.hadoop.hbase.replication/TestReplicationTrackerZKImpl/testPeerListChangedEvent/
> {code}
> Error Message
> test timed out after 30000 milliseconds
> Stacktrace
> java.lang.Exception: test timed out after 30000 milliseconds
> at java.lang.Thread.sleep(Native Method)
> at org.apache.hadoop.hbase.replication.TestReplicationTrackerZKImpl.testPeerListChangedEvent(TestReplicationTrackerZKImpl.java:170)
> {code}
> Looking at code, zk count run before we are set up to listen on event.
> Second test failure is symptom of this fail.
> I can't repro locally but happened on trunk and branch-1 just now.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)