[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657965#action_12657965
 ] 

Patrick Hunt commented on ZOOKEEPER-261:
----------------------------------------

Note to implementor/reviewers

1) be sure to LOG this situation in such a way that it can be debugged/tracked 
by end user (probably WARN level)
2) document this "feature" in the forrest documentation. Not sure what section 
but this might be a good place to talk about recovery, including this issue
http://hadoop.apache.org/zookeeper/docs/r3.0.1/zookeeperAdmin.html#sc_strengthsAndLimitations

esp as the details/questions are fresh in our mind re the discussion with 
Thomas on the user mailing list:
http://n2.nabble.com/What-happens-when-a-server-loses-all-its-state--td1664038.html
** summarizing this discussion into the strengths/limitations section of the 
forrest docs would be great!!


> Reinitialized servers should not participate in leader election
> ---------------------------------------------------------------
>
>                 Key: ZOOKEEPER-261
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-261
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: leaderElection, quorum
>            Reporter: Benjamin Reed
>
> A server that has lost its data should not participate in leader election 
> until it has resynced with a leader. Our leader election algorithm and 
> NEW_LEADER commit assumes that the followers voting on a leader have not lost 
> any of their data. We should have a flag in the data directory saying whether 
> or not the data is preserved so that the the flag will be cleared if the data 
> is ever cleared.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to