Skip to content

fix(elasticsearch): use configurable retry budget on the post-restart health wait #199

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.

Sign up for GitHub

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

Merged
Oddly merged 1 commit into from
Aug 12, 2026
Merged

fix(elasticsearch): use configurable retry budget on the post-restart health wait #199

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions roles/elasticsearch/tasks/elasticsearch-rolling-upgrade.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -331,8 +331,8 @@
((elasticsearch_response.json | default({})).status | default('')) in _elasticsearch_upgrade_health_statuses
and ((elasticsearch_response.json | default({})).number_of_nodes | default(0) | int)
>= _elasticsearch_upgrade_expected_nodes | int
retries: 30
delay: 30
retries: "{{ elasticsearch_upgrade_health_retries | int }}"
delay: "{{ elasticsearch_upgrade_health_delay | int }}"
vars:
# Same gate as the pre-node-down health wait so both sides of the
# rolling loop honour the same operator preference.
Expand Down
Loading