[
https://issues.apache.org/jira/browse/SOLR-12999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730693#comment-16730693
]
Noble Paul commented on SOLR-12999:
-----------------------------------
{quote}IndexFetcher that implements the change being proposed here...
{quote}
[~jason.j.b...@gmail.com] The proposed solution is as follows.
If a full replication is required,
# calculate the disk space required to copy all the segments
# If the space
# Check if the local disk has enough space with some ~10% margin. if the
master index is 100GB and the local disk has at-least 110GB free, the system
should behave exactly as it does today
# If the master-index has 100GB size and the local disk has only 90GB , the
segments can't be copied. See if we can delete the local index and get at least
110GB free space delete the local index first and download the segments from
master
Yes, there is a possibility of screw up and we need to address that separately.
> 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 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.
--
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
