You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michi Mutsuzaki (JIRA)" <ji...@apache.org> on 2014/03/14 03:46:42 UTC

[jira] [Updated] (ZOOKEEPER-1894) ObserverTest.testObserver fails consistently

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

Michi Mutsuzaki updated ZOOKEEPER-1894:
---------------------------------------

    Attachment: TEST-org.apache.zookeeper.test.ObserverTest.txt.gz

Attaching a gzipped log file with an additional log message to show that observer is calling QuorumPeer.getQuorumVerifier() many times.

{noformat}
diff --git src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java
index a60cf87..f959d86 100644
--- src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java
+++ src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java
@@ -1236,6 +1236,7 @@ public class QuorumPeer extends Thread implements QuorumStats.Provider {
      */

     public synchronized QuorumVerifier getQuorumVerifier(){
+        LOG.info("QuorumPeer.getQuorumVerifier() called.");
         return quorumVerifier;

     }
{noformat}

> 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)