[
https://issues.apache.org/jira/browse/SOLR-17692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SOLR-17692:
----------------------------------
Labels: pull-request-available (was: )
> DELETEREPLICA should preempt full-recovery instead of waiting for completion
> ----------------------------------------------------------------------------
>
> Key: SOLR-17692
> URL: https://issues.apache.org/jira/browse/SOLR-17692
> Project: Solr
> Issue Type: Bug
> Components: replication (java), SolrCloud
> Reporter: Jason Gerlowski
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I recently deleted a NRT replica that was in the middle of a full-recovery
> and was a bit surprised to see that the "delete" blocked waiting for the
> recovery to finish. This is a minor pain when the index is small, but
> becomes a huge waste of administrator time (and network bandwidth!) as index
> sizes grow.
> There's some plumbing in Solr that attempts to preempt recovery during a
> DELETE, but it appears that it seems that it mostly comes into play during
> peer-sync and "background replication" scenarios (i.e. PULL and TLOG replicas
> that do full-recovery during normal operation). Preemption doesn't seem to
> work once a recovering core is in the midst of a "full recovery". We should
> modify this code that it stops full-recovery as well, unless there's some
> compelling reason this was avoided in the initial implementation?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
