You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2014/04/02 20:18:24 UTC

[jira] [Assigned] (CURATOR-76) Adding leader selection ChildReaper recipe

     [ https://issues.apache.org/jira/browse/CURATOR-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jordan Zimmerman reassigned CURATOR-76:
---------------------------------------

    Assignee: Jordan Zimmerman

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