[prev in list] [next in list] [prev in thread] [next in thread] 

List:       solr-dev
Subject:    [jira] [Commented] (SOLR-12999) Index replication could delete segments first
From:       "ASF subversion and git services (JIRA)" <jira () apache ! org>
Date:       2019-01-31 21:18:00
Message-ID: JIRA.13199345.1542637784000.215682.1548969480383 () Atlassian ! JIRA
[Download RAW message or body]


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

ASF subversion and git services commented on SOLR-12999:
--------------------------------------------------------

Commit 34da61e863c459ae48103a3f6e1dacb76f14cd23 in lucene-solr's branch \
refs/heads/branch_8x from Noble Paul [ \
https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=34da61e ]

SOLR-12999: Index replication could delete segments before downloading segments from \
master if there is not enough disk space


> 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
> Assignee: Noble Paul
> Priority: Major
> Fix For: 8.0
> 
> Attachments: SOLR-12999.patch, SOLR-12999.patch
> 
> 
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]