Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
Date: Wed, 2 Apr 2014 19:02:14 +0000 (UTC)
From: "Jay Bae (JIRA)" <jira@apache.org>
To: dev@curator.apache.org
Message-ID: <JIRA.12681309.1385489678870.53042.1396465334840@arcas>
In-Reply-To: <JIRA.12681309.1385489678870@arcas>
References: <JIRA.12681309.1385489678870@arcas>
Subject: [jira] [Commented] (CURATOR-76) Adding leader selection ChildReaper
 recipe
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jay Bae commented on CURATOR-76:
--------------------------------

Thanks a lot Jordan.

> Adding leader selection ChildReaper recipe
> ------------------------------------------
>
>                 Key: CURATOR-76
>                 URL: https://issues.apache.org/jira/browse/CURATOR-76
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>            Reporter: Jay Bae
>            Assignee: Jordan Zimmerman
>             Fix For: 2.4.2
>
>         Attachments: CURATOR-76.patch
>
>
> We are having serious data corruption issue when we are rolling restart of zookeeper servers due to one application which is using ChildReaper recipe. I am not sure its root cause but my theory is, when the multiple instances are running ChildReaper recipe, they would conflict each other among checking exist and deleting paths. This conflict can cause data corruption. We observed all servers died due to corrupted data and we had to manually copy log/snapshot data and restart them.


--
This message was sent by Atlassian JIRA
(v6.2#6252)