[
https://issues.apache.org/jira/browse/SOLR-12999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693497#comment-16693497
]
Michael Braun commented on SOLR-12999:
--------------------------------------
Exactly - in the SolrCloud case where it can't PeerSync, index files need to be
shipped over for recovery, and that recovering replica shouldn't be serving
traffic (so the close of the searcher should be safe / it should have already
been closed).
The other use case for this is if you're using more than 50% hard drive,
copying index files could result in going out of disk.
Also one thing to note - fullCopy=false does not necessarily mean it won't copy
basically an entire full index over.
> Index replication could delete segments first
> ---------------------------------------------
>
> Key: SOLR-12999
> URL: https://issues.apache.org/jira/browse/SOLR-12999
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: replication (java)
> Reporter: David Smiley
> Priority: Major
>
> 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 only be useful if
> there is no SolrIndexSearcher open, since it would prevent the removal of
> files.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
