[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143198#comment-13143198
 ] 

Camille Fournier commented on ZOOKEEPER-1264:
---------------------------------------------

Ben, just two questions:
Does this logic really only apply to FollowerZookeeperServers or should 
observers also do this?

Why does the playing of these txns to the log come after we start the zk server 
instead of before?
                
> FollowerResyncConcurrencyTest failing intermittently
> ----------------------------------------------------
>
>                 Key: ZOOKEEPER-1264
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1264
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: tests
>    Affects Versions: 3.3.3, 3.4.0, 3.5.0
>            Reporter: Patrick Hunt
>            Assignee: Camille Fournier
>            Priority: Blocker
>             Fix For: 3.3.4, 3.4.0, 3.5.0
>
>         Attachments: ZOOKEEPER-1264-merge.patch, ZOOKEEPER-1264.patch, 
> ZOOKEEPER-1264.patch, ZOOKEEPER-1264.patch, ZOOKEEPER-1264.patch, 
> ZOOKEEPER-1264_branch33.patch, ZOOKEEPER-1264_branch34.patch, 
> ZOOKEEPER-1264unittest.patch, ZOOKEEPER-1264unittest.patch, 
> followerresyncfailure_log.txt.gz, logs.zip, tmp.zip
>
>
> The FollowerResyncConcurrencyTest test is failing intermittently. 
> saw the following on 3.4:
> {noformat}
> junit.framework.AssertionFailedError: Should have same number of
> ephemerals in both followers expected:<11741> but was:<14001>
>        at 
> org.apache.zookeeper.test.FollowerResyncConcurrencyTest.verifyState(FollowerResyncConcurrencyTest.java:400)
>        at 
> org.apache.zookeeper.test.FollowerResyncConcurrencyTest.testResyncBySnapThenDiffAfterFollowerCrashes(FollowerResyncConcurrencyTest.java:196)
>        at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:52)
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to