zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From afine <...@git.apache.org>
Subject [GitHub] zookeeper pull request #300: ZOOKEEPER-2807: Flaky test: org.apache.zookeepe...
Date Fri, 30 Jun 2017 22:55:12 GMT
GitHub user afine opened a pull request:


    ZOOKEEPER-2807: Flaky test: org.apache.zookeeper.test.WatchEventWhenAutoResetTest.testNodeDataChanged

    This failure appears to be related to ZOOKEEPER-2024. When a follower is syncing with
the leader and logging "the stuff that came in between the snapshot and the uptodate" we do
not wait for those commits to hit the db before starting the follower.
    In 3.6, we now have two separate queues in the CommitProcessor, it is possible that the
follower can serve requests before all of the commits from the leader have been applied. In
the case of this test failure we can set a watch in between a create and delete call. This
patch makes sure that the "delete" call will be committed before attempting to handle a client's
watcher request.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/afine/zookeeper ZOOKEEPER-2807

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #300
commit ca1774dca59d7a1c9e1d9e3c8391d21cf8c2c733
Author: Abraham Fine <afine@apache.org>
Date:   2017-06-30T22:44:26Z

    ZOOKEEPER-2807: Flaky test: org.apache.zookeeper.test.WatchEventWhenAutoResetTest.testNodeDataChanged


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message