lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SOLR-12999) Index replication could delete segments first
Date Wed, 08 May 2019 04:41:00 GMT

     [ https://issues.apache.org/jira/browse/SOLR-12999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Smiley resolved SOLR-12999.
---------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 8.2)
                       (was: master (9.0))
                   8.1

This issue should have been marked Resolved -- it was committed.  Since it was Open yet had
a fix-version, Ishan (RM for 8.1) bumped the version over to 8.2 from 8.1.  I'm looking at
the commit history now on branch_8_1 and I see these commits, and the CHANGES.txt is there
too.

I'm marking it Resolved and fixed in 8.1.  Also un-assigning fix-version of master since it's
implied; not a big deal.

> 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.1
>
>         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


Mime
View raw message