-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Reword docs on snapshot repo backup #115062
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
DaveCTurner
merged 1 commit into
elastic:main
from
DaveCTurner:2024/10/18/snapshot-repo-backup-reword
Oct 18, 2024
Merged
Reword docs on snapshot repo backup #115062
DaveCTurner
merged 1 commit into
elastic:main
from
DaveCTurner:2024/10/18/snapshot-repo-backup-reword
Oct 18, 2024
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
Because of elastic#93575 it's not sufficient to mark repositories with `readonly: true` while taking a backup. The only safe way to avoid writes is to completely unregister them.
Documentation preview: |
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-distributed (Team:Distributed) |
ywangd
approved these changes
Oct 18, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Oct 18, 2024
Because of elastic#93575 it's not sufficient to mark repositories with `readonly: true` while taking a backup. The only safe way to avoid writes is to completely unregister them.
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Oct 18, 2024
Because of elastic#93575 it's not sufficient to mark repositories with `readonly: true` while taking a backup. The only safe way to avoid writes is to completely unregister them.
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Oct 18, 2024
Because of elastic#93575 it's not sufficient to mark repositories with `readonly: true` while taking a backup. The only safe way to avoid writes is to completely unregister them.
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Oct 18, 2024
Because of elastic#93575 it's not sufficient to mark repositories with `readonly: true` while taking a backup. The only safe way to avoid writes is to completely unregister them.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 18, 2024
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 18, 2024
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 18, 2024
lkts
pushed a commit
to lkts/elasticsearch
that referenced
this pull request
Oct 18, 2024
Because of elastic#93575 it's not sufficient to mark repositories with `readonly: true` while taking a backup. The only safe way to avoid writes is to completely unregister them.
georgewallace
pushed a commit
to georgewallace/elasticsearch
that referenced
this pull request
Oct 25, 2024
Because of elastic#93575 it's not sufficient to mark repositories with `readonly: true` while taking a backup. The only safe way to avoid writes is to completely unregister them.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 28, 2024
jfreden
pushed a commit
to jfreden/elasticsearch
that referenced
this pull request
Nov 4, 2024
Because of elastic#93575 it's not sufficient to mark repositories with `readonly: true` while taking a backup. The only safe way to avoid writes is to completely unregister them.
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Jun 6, 2025
It's now ok to mark a repository as `readonly: true` while taking a backup, so this commit reinstates the docs that say this. Relates elastic#93575 Reverts elastic#115062 Reverts elastic#115071 Relates elastic#128296
This was referenced Jun 6, 2025
DaveCTurner
added a commit
to DaveCTurner/elastic-docs-content
that referenced
this pull request
Jun 6, 2025
It's now ok to mark a repository as `readonly: true` while taking a backup, so this commit reinstates the docs that say this. Relates elastic/elasticsearch#93575 Reverts elastic/elasticsearch#115062 Reverts elastic/elasticsearch#115071 Relates elastic/elasticsearch#128296 Relates elastic/elasticsearch#129040
DaveCTurner
added a commit
to elastic/docs-content
that referenced
this pull request
Jun 6, 2025
It's now ok to mark a repository as `readonly: true` while taking a backup, so this commit reinstates the docs that say this. Relates elastic/elasticsearch#93575 Reverts elastic/elasticsearch#115062 Reverts elastic/elasticsearch#115071 Relates elastic/elasticsearch#128296 Relates elastic/elasticsearch#129040
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jun 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-backport
Automatically create backport pull requests when merged
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>docs
General docs changes
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
Team:Docs
Meta label for docs team
v7.17.26
v8.15.4
v8.16.1
v8.17.0
v9.0.0
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.
Because of #93575 it's not sufficient to mark repositories with
readonly: true
while taking a backup. The only safe way to avoidwrites is to completely unregister them.