[
https://issues.apache.org/jira/browse/SOLR-18249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18130122#comment-18130122
]
Nick Shanin edited comment on SOLR-18249 at 10/22/26, 4:47 AM:
---------------------------------------------------------------
I have seen the symptom in this ticket in production (missing metadata) but it
was intermittent, incremental=false, and I was not able to reproduce it in a
test. Also, my PR does not survive scrutiny because a completed backup's
metadata is never overwritten. I am withdrawing my PR and will keep trying to
reproduce this issue or read the code to track it down.
was (Author: JIRAUSER314749):
I have seen the symptom in this ticket in production (missing metadata) but it
was intermittent and I was not able to reproduce it in a test. Also, my PR does
not survive scrutiny because a completed backup's metadata is never
overwritten. I am withdrawing my PR and will keep trying to reproduce this
issue.
> Fix non-atomic write in ShardBackupMetadata.store() that can destroy backup
> metadata
> ------------------------------------------------------------------------------------
>
> Key: SOLR-18249
> URL: https://issues.apache.org/jira/browse/SOLR-18249
> Project: Solr
> Issue Type: Bug
> Reporter: Mark Robert Miller
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Make atomic for S3 and GCS, reduce chance for LocalFS.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
