Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
From: revans2 <git@git.apache.org>
To: dev@zookeeper.apache.org
Reply-To: dev@zookeeper.apache.org
References: <git-pr-157-zookeeper@git.apache.org>
In-Reply-To: <git-pr-157-zookeeper@git.apache.org>
Subject: [GitHub] zookeeper issue #157: ZOOKEEPER-2678: Discovery and Sync can take a very lon...
Content-Type: text/plain
Message-Id: <20170213145550.322C6DFC31@git1-us-west.apache.org>
Date: Mon, 13 Feb 2017 14:55:50 +0000 (UTC)
archived-at: Mon, 13 Feb 2017 14:55:52 -0000

Github user revans2 commented on the issue:

    https://github.com/apache/zookeeper/pull/157
  
    @rakeshadr If it makes you feel any better we have been running with an older version of this patch in production for a while.  We have used it as part of a rolling upgrade at least 10 times in production where if it were not there we would have had some very painful outages. 
    
    I have also manually tested it at least 50 times shooting the leader under load (10,000 operations/second) on a 3.4 GB DB, watching it recover, and then validating the integrity of the DB to be sure we didn't get any corruption.


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