Optionally make S3 writes unconditional #138735
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As of elastic#133030 Elasticsearch uses S3's support for conditional writes to protect against repository corruption. It is possible that some other storage system may claim to be fully S3-compatible despite rejecting such requests. This commit adds a repository setting that allows to make all writes unconditional, unsafely disabling the corruption protection, but allowing users some time to work with their storage supplier to address the incompatibility. Backport of elastic#137185 and elastic#138406 to 9.2
DaveCTurner
added
>non-issue
:Distributed Coordination/Snapshot/Restore
Contributor
Author
|
I thought that #133030 landed in 9.3.0 but I was remembering wrong, it actually took effect in 9.2.0, so we need to backport this change to the 9.2 series too. |
DaveCTurner
added a commit
to DaveCTurner/elastic-docs-content
that referenced
this pull request
Nov 28, 2025
This change was backported to 9.2.3 in elastic/elasticsearch#138735, updating the `applies_to` marker to match.
DaveCTurner
added a commit
to elastic/docs-content
that referenced
this pull request
Nov 28, 2025
) This change was backported to 9.2.3 in elastic/elasticsearch#138735, updating the `applies_to` marker to match.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As of #133030 Elasticsearch uses S3's support for conditional writes to
protect against repository corruption. It is possible that some other
storage system may claim to be fully S3-compatible despite rejecting
such requests.
This commit adds a repository setting that allows to make all writes
unconditional, unsafely disabling the corruption protection, but
allowing users some time to work with their storage supplier to address
the incompatibility.
Backport of #137185 and #138406 to 9.2