Increase replica_unassigned_buffer_time default from 3s to 5s#112834
Merged
parkertimmins merged 2 commits intoelastic:mainfrom Sep 12, 2024
Merged
Conversation
elasticsearchmachine
added
needs:triage
parkertimmins
added
:Distributed/Health
elasticsearchmachine
added
the
Team:Data Management (obsolete)
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
Collaborator
|
Hi @parkertimmins, I've created a changelog YAML for you. |
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
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.
#112066 changed the way we calculate if all replicas are unassigned when primary is recently created, specifically on serverless. That PR included a new setting,
health.shards_availability.replica_unassigned_buffer_time, with a default value of 3 seconds. This PR increases the default value to 5 seconds as it will keep more shards from going red transiently, while still being low enough to go red quickly if there is an actual availability issue.