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
CCR: Use local cluster state request #100323
Merged
henningandersen
merged 2 commits into
elastic:main
from
henningandersen:fix_auto_follow_use_local_cluster_state_request
Oct 9, 2023
Merged
CCR: Use local cluster state request #100323
henningandersen
merged 2 commits into
elastic:main
from
henningandersen:fix_auto_follow_use_local_cluster_state_request
Oct 9, 2023
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
Auto following indices from leader asks for the cluster state waiting for the next version to be available. These requests are no longer being forwarded to the master on the leader cluster, since waiting for the state to appear on the coordinator is equally good and avoids burdening the master with serializing a potentially large cluster state.
henningandersen
added
>bug
:Distributed/CCR
Issues around the Cross Cluster State Replication features
v8.11.1
v8.12.0
labels
Oct 5, 2023
Pinging @elastic/es-distributed (Team:Distributed) |
Hi @henningandersen, I've created a changelog YAML for you. |
tlrx
approved these changes
Oct 9, 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
henningandersen
added
the
auto-backport-and-merge
Automatically create backport pull requests and merge when ready
label
Oct 9, 2023
💚 Backport successful
|
henningandersen
added a commit
to henningandersen/elasticsearch
that referenced
this pull request
Oct 9, 2023
Auto following indices from leader asks for the cluster state waiting for the next version to be available. These requests are no longer being forwarded to the master on the leader cluster, since waiting for the state to appear on the coordinator is equally good and avoids burdening the master with serializing a potentially large cluster state.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 9, 2023
Auto following indices from leader asks for the cluster state waiting for the next version to be available. These requests are no longer being forwarded to the master on the leader cluster, since waiting for the state to appear on the coordinator is equally good and avoids burdening the master with serializing a potentially large cluster state.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-backport-and-merge
Automatically create backport pull requests and merge when ready
>bug
:Distributed/CCR
Issues around the Cross Cluster State Replication features
Team:Distributed
Meta label for distributed team
v8.11.1
v8.12.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.
Auto following indices from leader asks for the cluster state waiting for the next version to be available. These requests are no longer being forwarded to the master on the leader cluster, since waiting for the state to appear on the coordinator is equally good and avoids burdening the master with serializing a potentially large cluster state.