[
https://issues.apache.org/jira/browse/SOLR-13872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris M. Hostetter updated SOLR-13872:
--------------------------------------
Attachment: SOLR-13872.patch
Status: Open (was: Open)
Ok, here's a patch with the API/Usage changes I think we should make.
There are still a lot of nocommits, but mostly just related to additional test
coverage I want to add (and most of that is around named snapshots since i
didn't dig into that very deep and i want to make sure taking backups that way
is as solid as the "simple" path) but I think the new API & synchornization
logic is pretty solid.
There's also a few places were I have nocommits related to needing to spin out
loosly related jiras. Once I've done that i'll slim down this patch a bit and
link those jiras and then finish up the tests.
> Backup can fail to read index files w/NoSuchFileException during merges
> (SOLR-11616 regression)
> ------------------------------------------------------------------------------------------------
>
> Key: SOLR-13872
> URL: https://issues.apache.org/jira/browse/SOLR-13872
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Chris M. Hostetter
> Assignee: Chris M. Hostetter
> Priority: Major
> Attachments: SOLR-13872.patch, SOLR-13872.patch, index_churn.pl
>
>
> SOLR-11616 purports to fix a bug in Solr's backup functionality that causes
> 'NoSuchFileException' errors when attempting to backup an index while it is
> undergoing indexing (and segment merging)
> Although SOLR-11616 is marked with "Fix Version: 7.2" it's pretty easy to
> demonstrate that this bug still exists on master, branch_8x, and even in 7.2
> - so it seems less like the current problem is a "regression" and more that
> the original fix didn't work.
> ----
> The crux of the problem seems to be concurrency bugs in if/how a commit is
> "reserved" before attempting to copy the files in that commit to the backup
> location.
> A possible work around discussed in more depth in the comments below is to
> update {{solrconfig.xml}} to explicitly configure the {{SolrDeletionPolicy}}
> with either the {{maxCommitsToKeep}} or {{maxCommitAge}} options to ensure
> the commits are kept around long enough for the backup to be created.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
