You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2010/03/09 19:21:27 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 ]

Patrick Hunt updated ZOOKEEPER-675:
-----------------------------------

         Priority: Critical  (was: Major)
    Fix Version/s:     (was: 3.4.0)
                   3.3.0
         Assignee: Henry Robinson

Henry can you look at this ASAP? Ben says that this is happening every 3rd time he runs the tests on his system. We really should address this to minimize false positive test failures in 3.3.0 (ben thinks the test itself is broken, not the code).

> 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 Paiva Junqueira
>            Assignee: Henry Robinson
>            Priority: Critical
>             Fix For: 3.3.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.
-
You can reply to this email to add a comment to the issue online.