[
https://issues.apache.org/jira/browse/SOLR-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922247#action_12922247
]
Hoss Man commented on SOLR-2174:
--------------------------------
Note: i personally don't fully understand the issue, but i noticed the message
was unreplied and had a patch so i wanted to make sure if got tracked in Jira
> commit durring backup of more then 10 seconds causes snapshoot to fail ?
> ------------------------------------------------------------------------
>
> Key: SOLR-2174
> URL: https://issues.apache.org/jira/browse/SOLR-2174
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
> Affects Versions: 1.4.1
> Reporter: Hoss Man
>
> Comment from Peter Sturge in email...
> http://lucene.472066.n3.nabble.com/commitReserveDuration-backups-and-saveCommitPoint-td1407399.html
> {quote}
> In Solr 1.4 and 1.4.1, the SOLR-1475 patch is certainly there, but I don't
> believe it truly addresses the problem.
> Here's why:
> When a 'backup' command is received by the RemplicationHandler, it creates a
> SnapShooter instance and asynchronously does a full file snapshot of the
> current commit point.
> The current commit version to which this refers, however, is set to be
> cleared on the next commit by the value of 'commitReserveDuration', which, by
> default, is set to 10secs. (see cleanReserves() in
> IndexDeletionPolicyWrapper.java).
> If you perform a backup and no commits occur during this time, it's fine,
> because clearReserves() is not called. If you do get a commit during the
> backup process, and the backup takes longer than 10secs,
> the whole snapshot operation fails (because delete() doesn't see the commit
> point in savedCommits - see below).
> {quote}
> Peter's email mentions two patches that he believes will fix this problem
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
