You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@solr.apache.org by "Nick Shanin (Jira)" <ji...@apache.org> on 2026/10/22 04:31:00 UTC

[jira] [Commented] (SOLR-18249) Fix non-atomic write in ShardBackupMetadata.store() that can destroy backup metadata

    [ https://issues.apache.org/jira/browse/SOLR-18249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18130122#comment-18130122 ] 

Nick Shanin commented on SOLR-18249:
------------------------------------

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: 10m
>  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: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org