curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-76) Adding leader selection ChildReaper recipe
Date Sun, 30 Mar 2014 19:07:15 GMT

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

Jordan Zimmerman commented on CURATOR-76:
-----------------------------------------

This change makes the leader a requirement. It would be better (considering backward compatibility)
to make the leader optional. Please supply a patch with an optional leader.

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

Mime
View raw message