[
https://issues.apache.org/jira/browse/SOLR-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151280#comment-13151280
]
Yonik Seeley commented on SOLR-2808:
------------------------------------
Thinking about the full index copy, we need to ensure there's not a window for
potentially missed updates. One way to do this is:
1. leader should ensure that future updates will be forwarded to the
recovering node (i.e. recovering node should be visible in ZK and the leader's
model should contain that node).
2. leader should then do a hard commit
3. index copy from leader to recovering node can commence
> Node Recovery
> -------------
>
> Key: SOLR-2808
> URL: https://issues.apache.org/jira/browse/SOLR-2808
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Yonik Seeley
> Fix For: 4.0
>
>
> Node recovery encompasses everything involved in getting a node to the
> "active" state after coming (back) up.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
