[
https://issues.apache.org/jira/browse/ZOOKEEPER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879967#action_12879967
]
Mike Solomon commented on ZOOKEEPER-335:
----------------------------------------
I am having this exact issue, but I am not upgrading. I am merely restarting
the cluster.
I have a cluster of three. I took down host1 and verified that my application
remained and reconnected to host2 and host3.
With host1 back online, I took down host2. I noticed that the java process was
spinning over 100% CPU and realized it had not come back up.
This is running the 3.3.0 JAR release on a dual proc, quad-core Intel box. I'm
running SuSE 10.3, 64-bit, with this version of java:
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode)
I will attach a log file.
> zookeeper servers should commit the new leader txn to their logs.
> -----------------------------------------------------------------
>
> Key: ZOOKEEPER-335
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-335
> Project: Zookeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.1.0
> Reporter: Mahadev konar
> Assignee: Mahadev konar
> Priority: Blocker
> Fix For: 3.4.0
>
>
> currently the zookeeper followers do not commit the new leader election. This
> will cause problems in a failure scenarios with a follower acking to the same
> leader txn id twice, which might be two different intermittent leaders and
> allowing them to propose two different txn's of the same zxid.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
