Elasticsearch Version
8.5
Installed Plugins
No response
Java Version
bundled
OS Version
Darwin
Problem Description
The disk indicator is currently diagnosing both blocked indices and nodes that run out of disk space.
However, it's only the affected nodes that are reported as affected as part of the affected_resources field.
This proposes we fix this by reporting all affected resources under multiple types e.g.
"affected_resources": {
"indices": ["index-1", "index-2"],
"nodes": [
{"id": "id1", "name": "node-1"},
{"id": "id2", "name": "node-2"}
],
"repositories": ["repository-1", "repository-2"],
"slm_policies": ["every-30-minutes"],
...
}
Steps to Reproduce
GET _internal/_health against a data node that has surpassed the flood stage watermark and is hosting indices.
Logs (if relevant)
No response
Elasticsearch Version
8.5
Installed Plugins
No response
Java Version
bundled
OS Version
Darwin
Problem Description
The disk indicator is currently diagnosing both blocked indices and nodes that run out of disk space.
However, it's only the affected nodes that are reported as affected as part of the
affected_resourcesfield.This proposes we fix this by reporting all affected resources under multiple types e.g.
Steps to Reproduce
GET _internal/_healthagainst a data node that has surpassed the flood stage watermark and is hosting indices.Logs (if relevant)
No response