Skip to content
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

Increase replica_unassigned_buffer_time default from 3s to 5s #112834

Conversation

parkertimmins
Copy link
Contributor

#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.

@elasticsearchmachine elasticsearchmachine added needs:triage Requires assignment of a team area label v9.0.0 labels Sep 12, 2024
Copy link
Contributor

@mattc58 mattc58 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@parkertimmins parkertimmins added :Data Management/Health >enhancement and removed needs:triage Requires assignment of a team area label labels Sep 12, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Data Management Meta label for data/management team label Sep 12, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

@elasticsearchmachine
Copy link
Collaborator

Hi @parkertimmins, I've created a changelog YAML for you.

@parkertimmins parkertimmins merged commit 96ac4f6 into elastic:main Sep 12, 2024
15 checks passed
@parkertimmins parkertimmins deleted the change-shard-availility-buffer-time-value branch September 12, 2024 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants