![Could not retrieve Elasticsearch cluster health. Fetching Elasticsearch cluster health failed: There was an error fetching a resource: Internal Server Error. Additional information: Couldn't read Elasticsearch cluster health - Graylog Central (peer Could not retrieve Elasticsearch cluster health. Fetching Elasticsearch cluster health failed: There was an error fetching a resource: Internal Server Error. Additional information: Couldn't read Elasticsearch cluster health - Graylog Central (peer](https://global.discourse-cdn.com/business6/uploads/graylog/original/2X/7/72c974b6c9978764816552c7df2ffbe1ce1145be.png)
Could not retrieve Elasticsearch cluster health. Fetching Elasticsearch cluster health failed: There was an error fetching a resource: Internal Server Error. Additional information: Couldn't read Elasticsearch cluster health - Graylog Central (peer
![Achieving a Green Status in Elasticsearch: Resolving the Yellow Status in a Single Node Cluster | by Stuart Macfarlane | Medium Achieving a Green Status in Elasticsearch: Resolving the Yellow Status in a Single Node Cluster | by Stuart Macfarlane | Medium](https://miro.medium.com/v2/resize:fit:608/1*F1jgUOW-3ZM00IJBOnQIhg.png)
Achieving a Green Status in Elasticsearch: Resolving the Yellow Status in a Single Node Cluster | by Stuart Macfarlane | Medium
![AWS Elasticsearch cluster health status yellow then red after increasing the number of nodes | by Saket Jain | Medium AWS Elasticsearch cluster health status yellow then red after increasing the number of nodes | by Saket Jain | Medium](https://miro.medium.com/v2/resize:fit:1400/1*zeRMJM6254Y9453Xk9BlDQ.png)