lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-8372) Canceled recovery can lead to data loss
Date Thu, 10 Dec 2015 12:43:11 GMT

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

Mark Miller commented on SOLR-8372:
-----------------------------------

Buffering seems fine to me. Now that we start buffering even before peer sync anyway, we are
almost always in a buffering state anyway, other than the brief time between replaying buffered
docs and starting the recovery again.

> Canceled recovery can lead to data loss
> ---------------------------------------
>
>                 Key: SOLR-8372
>                 URL: https://issues.apache.org/jira/browse/SOLR-8372
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Yonik Seeley
>
> A recovery via index replication tells the update log to start buffering updates.  If
that recovery is canceled for whatever reason by the replica, the RecoveryStrategy calls ulog.dropBufferedUpdates()
which stops buffering and places the UpdateLog back in active mode.  If updates come from
the leader after this point (and before ReplicationStrategy retries recovery), the update
will be processed as normal and added to the transaction log. If the server is bounced, those
last updates to the transaction log look normal (no FLAG_GAP) and can be used to determine
who is more up to date. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message