You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2011/06/15 08:03:47 UTC

[jira] [Updated] (ZOOKEEPER-675) LETest thread fails to join

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mahadev konar updated ZOOKEEPER-675:
------------------------------------

    Fix Version/s:     (was: 3.4.0)
                   3.5.0

not a blocker. Moving it out of 3.4 release.

> LETest thread fails to join
> ---------------------------
>
>                 Key: ZOOKEEPER-675
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-675
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: leaderElection
>            Reporter: Flavio Junqueira
>            Assignee: Henry Robinson
>            Priority: Critical
>             Fix For: 3.5.0
>
>         Attachments: TEST-org.apache.zookeeper.test.LETest.txt
>
>
> After applying the patch of ZOOKEEPER-569, I observed a failure of LETest. From a cursory inspection of the log, I can tell that a leader is being elected, but some thread is not joining. At this point I'm not sure if this is a problem with the leader election implementation or the test itself. 
> Just to be clear, the patch of ZOOKEEPER-569 solved a real issue, but it seems that there is yet another problem with LETest.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira