[
https://issues.apache.org/jira/browse/ZOOKEEPER-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flavio Paiva Junqueira updated ZOOKEEPER-675:
---------------------------------------------
Description:
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.
was:
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. I'm not sure
Just to be clear, the patch of ZOOKEEPER-569 solved a real issue, but it seems
that there is yet another problem with LETest.
> 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
> Fix For: 3.4.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.
