[
https://issues.apache.org/jira/browse/ZOOKEEPER-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077413#comment-16077413
]
Alexander Shraer commented on ZOOKEEPER-2807:
---------------------------------------------
ZOOKEEPER-2684 is unrelated, but but also makes changes to the same file.
Intuitively this may not be the right place for such a fix - this probably
should be higher level - making sure that follower does not even accept local
ops before properly completing the sync. Even if you drain the
committedRequests, I'm not sure that guarantees that there are no more that
will arrive.
I think @breed may have a solution for this problem, lets wait for him to
comment.
> Flaky test:
> org.apache.zookeeper.test.WatchEventWhenAutoResetTest.testNodeDataChanged
> -------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2807
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2807
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Abraham Fine
> Assignee: Abraham Fine
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
