The status of my Elasticsearch cluster as displayed in the Monitoring tab of the Amazon Elasticsearch Service console is red. How do I troubleshoot this?

A red cluster status indicates that both primary and replica shards are not allocated to nodes in your cluster, as described in Monitoring Domains with Amazon CloudWatch Metrics. No additional automatic snapshots are taken, even of healthy indices, while the red cluster status persists. This state is commonly caused by the following:

  • Data nodes in the Elasticsearch cluster lack free storage space.
  • The Elasticsearch process crashed due to a continuous heavy processing load on a data node.

Note: The status of a cluster as displayed in the Monitoring tab of the Amazon Elasticsearch Service console might not directly correlate to the observed performance or stability of the cluster. In some cases, a cluster with a status of green might not perform as expected, and a cluster with a status of red might appear to function well with the exception of requests to degraded indices.

You must take action if the red cluster status is caused by a lack of free storage space or a heavy processing load. Most cluster recovery scenarios require that you delete red indices.

Lack of Free Storage Space

To determine if your red cluster status is caused by a lack of free storage space and for the appropriate steps to resolve this issue, see Recovering from a Lack of Free Storage Space.

Note: Elasticsearch reserves 10 to 20% of storage space on each instance for internal operations. Consider this when configuring storage for Elasticsearch cluster instances.

Continuous Heavy Processing Load

To determine if your red cluster status is caused by a continuous heavy processing load and for the appropriate steps to resolve this issue, see Recovering from a Continuous Heavy Processing Load.

Amazon API Gateway, AWS Lambda, body mapping template, Node.js, integration, custom headers, function, resource, stage, deploy, request body


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2016-10-07