-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Add troubleshooting guide for corrupt repository #88391
Conversation
Pinging @elastic/es-data-management (Team:Data Management) |
Pinging @elastic/es-docs (Team:Docs) |
@@ -0,0 +1,11 @@ | |||
[[add-repository]] | |||
== Mark repository as read-only in other deployments and re-create it in this deployment |
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.
I don't like this title. Any better suggestions?
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.
In troubleshooting pages, the title typically denotes the problem that the user is encountering and trying to solve. In which case, maybe something like Multiple deployments writing to the same repository could be a good title.
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.
Thanks for the suggestion Adam. I'll make this change.
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.
I left some general comments, I think we should replace "re-add" with "recreate" since re-add is an awkward semi-not-really-a-word-word.
Otherwise, this is a semi-complicated remediation, so I'm not sure how to simplify it more.
we want to keep writing to the repository the "main" deployment (the current cluster), | ||
and the other one(s) where we'll mark the repository as read-only the "secondary" |
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.
we want to keep writing to the repository the "main" deployment (the current cluster), | |
and the other one(s) where we'll mark the repository as read-only the "secondary" | |
we want to keep writing to the repository the "primary" deployment (the current cluster), | |
and the other one(s) where we'll mark the repository as read-only the "secondary" |
Feels like if we go with "secondary" maybe we should use "primary" also?
docs/reference/tab-widgets/troubleshooting/snapshot/corrupt-repository.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/tab-widgets/troubleshooting/snapshot/corrupt-repository.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/tab-widgets/troubleshooting/snapshot/corrupt-repository.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/tab-widgets/troubleshooting/snapshot/corrupt-repository.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/tab-widgets/troubleshooting/snapshot/corrupt-repository.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/tab-widgets/troubleshooting/snapshot/corrupt-repository.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/tab-widgets/troubleshooting/snapshot/corrupt-repository.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/tab-widgets/troubleshooting/snapshot/corrupt-repository.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/tab-widgets/troubleshooting/snapshot/corrupt-repository.asciidoc
Outdated
Show resolved
Hide resolved
…pository.asciidoc Co-authored-by: Lee Hinman <[email protected]>
…pository.asciidoc Co-authored-by: Lee Hinman <[email protected]>
…pository.asciidoc Co-authored-by: Lee Hinman <[email protected]>
…pository.asciidoc Co-authored-by: Lee Hinman <[email protected]>
…pository.asciidoc Co-authored-by: Lee Hinman <[email protected]>
…pository.asciidoc Co-authored-by: Lee Hinman <[email protected]>
…pository.asciidoc Co-authored-by: Lee Hinman <[email protected]>
…pository.asciidoc Co-authored-by: Lee Hinman <[email protected]>
Co-authored-by: Lee Hinman <[email protected]>
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, I left a few more nits, but up to you. Thanks for writing these!
docs/reference/tab-widgets/troubleshooting/snapshot/corrupt-repository.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/tab-widgets/troubleshooting/snapshot/corrupt-repository.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/tab-widgets/troubleshooting/snapshot/corrupt-repository.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/tab-widgets/troubleshooting/snapshot/corrupt-repository.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/troubleshooting/snapshot/add-repository.asciidoc
Outdated
Show resolved
Hide resolved
Co-authored-by: Lee Hinman <[email protected]>
@elasticmachine update branch |
Co-authored-by: Lee Hinman <[email protected]>
💚 Backport successful
|
Co-authored-by: Lee Hinman <[email protected]> Co-authored-by: Lee Hinman <[email protected]>
* upstream/master: (2974 commits) Reserved cluster state service (elastic#88527) Add transport action immutable state checks (elastic#88491) Remove suggest flag from index stats docs (elastic#85479) Polling cluster formation state for master-is-stable health indicator (elastic#88397) Add test execution guide in yamlRestTest asciidoc (elastic#88490) Add troubleshooting guide for corrupt repository (elastic#88391) [Transform] Finetune Schedule to be less noisy on retry and retry slower (elastic#88531) Updatable API keys - auto-update legacy RDs (elastic#88514) Fix typo in TransportForceMergeAction and TransportClearIndicesCacheA… (elastic#88064) Fixed NullPointerException on bulk request (elastic#88358) Avoid needless index metadata builders during reroute (elastic#88506) Set metadata on request in API key noop test (elastic#88507) Fix passing positional args to ES in Docker (elastic#88502) Improve description for task api detailed param (elastic#88493) Support cartesian shape with doc values (elastic#88487) Promote usage of Subjects in Authentication class (elastic#88494) Add CCx 2.0 feature flag (elastic#88451) Reword the watcher 'always' and 'never' condition docs (elastic#86105) Simplify azure discovery installation docs (elastic#88404) Breakup FIPS CI testing jobs ... # Conflicts: # server/src/main/java/org/elasticsearch/index/mapper/NumberFieldMapper.java # x-pack/plugin/mapper-aggregate-metric/src/main/java/org/elasticsearch/xpack/aggregatemetric/mapper/AggregateDoubleMetricFieldMapper.java
This adds a troubleshooting guide for the situation when multiple clusters
are writing to the same snapshot repository, resulting in a corrupt repository.
Preview link https://elasticsearch_88391.docs-preview.app.elstc.co/guide/en/elasticsearch/reference/master/add-repository.html