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

Check ElasticSearch cluster health in admin dashboard #26417

Closed
renchap opened this issue Aug 9, 2023 · 0 comments · Fixed by #26448
Closed

Check ElasticSearch cluster health in admin dashboard #26417

renchap opened this issue Aug 9, 2023 · 0 comments · Fixed by #26448
Labels
area/search suggestion Feature suggestion

Comments

@renchap
Copy link
Sponsor Member

renchap commented Aug 9, 2023

Pitch

In addition to the version check, we should also check the cluster status (client.cluster.health["status"]) and show a warning/error if it is yellow/red.

A yellow status usually means that replicas are not assigned (one of your nodes are down?), red usually means that shard data is not available and that search is not working properly, or not at all, and your cluster is very unhealthy.

Motivation

I suspect many people deployed ElasticSearch on their instance, but do not have proper monitoring in place and do not know that their cluster is having issues, causing search to either not work, work on only some data, or is very slow.

Note: this should only be done after the recent work on setting the proper count for shards/replica is done, as at the moment every single-node ES cluster would be yellow as Mastodon always sets number_of_replicas to 1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/search suggestion Feature suggestion
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant