-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Update doc as per SDH finding #101285
Merged
Merged
Update doc as per SDH finding #101285
Conversation
This file contains 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
Documentation preview: |
elasticsearchmachine
added
the
needs:triage
Requires assignment of a team area label
label
Oct 24, 2023
elasticsearchmachine
added
Team:Docs
Meta label for docs team
and removed
needs:triage
Requires assignment of a team area label
labels
Oct 24, 2023
Pinging @elastic/es-docs (Team:Docs) |
jrodewig
approved these changes
Oct 24, 2023
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. Thanks!
This was referenced May 23, 2024
shainaraskas
pushed a commit
to shainaraskas/elasticsearch
that referenced
this pull request
May 23, 2024
(cherry picked from commit 66f7298)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
shainaraskas
pushed a commit
to shainaraskas/elasticsearch
that referenced
this pull request
May 23, 2024
(cherry picked from commit 66f7298)
shainaraskas
pushed a commit
to shainaraskas/elasticsearch
that referenced
this pull request
May 23, 2024
(cherry picked from commit 66f7298)
shainaraskas
pushed a commit
to shainaraskas/elasticsearch
that referenced
this pull request
May 23, 2024
(cherry picked from commit 66f7298)
shainaraskas
added a commit
that referenced
this pull request
May 23, 2024
(cherry picked from commit 66f7298) Co-authored-by: Volodymyr Krasnikov <[email protected]>
shainaraskas
added a commit
that referenced
this pull request
May 23, 2024
(cherry picked from commit 66f7298) Co-authored-by: Volodymyr Krasnikov <[email protected]>
shainaraskas
added a commit
that referenced
this pull request
May 23, 2024
(cherry picked from commit 66f7298) Co-authored-by: Volodymyr Krasnikov <[email protected]>
shainaraskas
added a commit
that referenced
this pull request
May 23, 2024
(cherry picked from commit 66f7298) Co-authored-by: Volodymyr Krasnikov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If customer follows strictly to current Tutorial: Disaster recovery based on bi-directional cross-cluster replication it is possible to fall into recursive auto-following trap.
In order to work properly
leader_index_exclusion_patterns
must use wildcard rather than templateWorking setup (assuming clusterA and clusterB have bi-directional link)