[
https://issues.apache.org/jira/browse/ZOOKEEPER-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934647#comment-13934647
]
Raul Gutierrez Segales commented on ZOOKEEPER-1894:
---------------------------------------------------
bq. It looks like the observer is sending a lot of messages to itself during
the leader election.
Trunk currently has a bug by which Observers enter a notification loop, see:
https://issues.apache.org/jira/browse/ZOOKEEPER-1807
We had to patch this to run it in prod.
> ObserverTest.testObserver fails consistently
> --------------------------------------------
>
> Key: ZOOKEEPER-1894
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1894
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum
> Affects Versions: 3.5.0
> Environment: ubuntu 13.10
> Server environment:java.version=1.7.0_51
> Server environment:java.vendor=Oracle Corporation
> Reporter: Michi Mutsuzaki
> Fix For: 3.5.0
>
> Attachments: TEST-org.apache.zookeeper.test.ObserverTest.txt.gz
>
>
> ObserverTest.testObserver fails consistently on my box. It looks like the
> observer (myid:3) calls QuorumPeer.getQuorumVerifier() in a tight loop, and
> the leader (myid:2) is not getting enough CPU time to synchronize with the
> follower and the observer. The test passes if I increase
> ClientBase.CONNECTION_TIMEOUT from 30 seconds to 120 seconds. I'll attach a
> log file.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
