[SOLR-12999] Index replication could delete segments first

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 8.1
• Component/s: replication (java)
• Assignee: Noble Paul
• Reporter: David Smiley
• Created: 19/Nov/18 14:29
• Updated: 08/Jun/19 15:01
• Resolved: 08/May/19 04:40

Description

Index replication could optionally delete files that it knows will not be needed first. This would reduce disk capacity requirements of Solr, and it would reduce some disk fragmentation when space get tight.

Solr (IndexFetcher) already grabs the remote file list, and it could see which files it has locally, then delete the others. Today it asks Lucene to deleteUnusedFiles at the end. This new mode would probably only be useful if there is no SolrIndexSearcher open, since it would prevent the removal of files.

The motivating scenario is a SolrCloud replica that is going into full recovery. It ought to not be fielding searches. The code changes would not depend on SolrCloud though.

This option would have some danger the user should be aware of. If the replication fails, leaving the local files incomplete/corrupt, the only recourse is to try full replication again. You can't just give up and field queries.

Issue Links

• is related to: SOLR-13474 Fix "Search is temporarily disabled" logic to be consistent for entire request
• relates to: SOLR-13469 rejected requests during ful IndexFetch should not use 403 response code