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

.alerts-* auto-expand replicas 0-1 #139864

Closed
kobelb opened this issue Aug 31, 2022 · 2 comments · Fixed by #140335
Closed

.alerts-* auto-expand replicas 0-1 #139864

kobelb opened this issue Aug 31, 2022 · 2 comments · Fixed by #140335
Assignees
Labels
bug Fixes for quality problems that affect the customer experience sdh-linked Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@kobelb
Copy link
Contributor

kobelb commented Aug 31, 2022

Currently, the .alerts-* are being created with with number_of_replicas: 1. This will cause clusters that only have a single Elasticsearch node to always appear unhealthy because they can't create a replica. Instead, we should change the .alerts-* indices to have auto_expand_replicas: 0-1 to make clusters with a single Elasticsearch node healthy, but expand to a single replica as soon as there is a second node. This is similar to how we handle the .kibana_* indices.

@kobelb kobelb added bug Fixes for quality problems that affect the customer experience Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Aug 31, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@nerophon
Copy link
Contributor

@doakalexi thanks for working on the PR to fix this. Is there any possibility this could please also be back-ported into the next 7.17 release? Thank you. cc @kobelb .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience sdh-linked Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

5 participants