[
https://issues.apache.org/jira/browse/SOLR-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161388#comment-13161388
]
Mark Miller commented on SOLR-2808:
-----------------------------------
To update what's done here:
I've taken what Yonik has done in SOLR-2700 and implemented basic replication
recovery.
When a new replica comes up, or a node goes down and comes back, recovery is
triggered. The recovery process issues a commit to the leader, starts buffering
updates to the transaction log, and does a replication. Then it replays the
buffered updates.
This gives us working recovery. Eventually, we will want to use realtime-get to
do a faster recovery when the node has not been down for long - that's really
just an optimization though.
I'm still slaving away on getting good tests for this, but its up and working
which is pretty sweet.
> 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
>
> Attachments: TEST-org.apache.solr.cloud.RecoveryZkTest.xml
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
