lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Commented] (SOLR-12999) Index replication could delete segments first
Date Tue, 14 May 2019 21:41:01 GMT


Hoss Man commented on SOLR-12999:

FYI: while fixing TestReplicationHandlerDiskOverFlow to prevent some cncurrency related failures
that have popped up in recent jenkins builds, i've uncovered 3 related issues that i've filed
which people following this may be interested in...

* SOLR-13469 - rejected requests during ful IndexFetch should not use 403 response code
* SOLR-13470 - SolrException msg not always propogated to HttpClient (may be specific to SOLR-12999
* SOLR-13471 - javabin codec can marshal data that it can't unmarshal (ClassCastException:
class java.lang.Boolean cannot be cast to class java.lang.String)

> Index replication could delete segments first
> ---------------------------------------------
>                 Key: SOLR-12999
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message