1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
OpenSearch dashboard can go into red state for following reasons:
- Node failure caused by an issue with an Amazon Elastic Compute Cloud (Amazon EC2) instance or Amazon Elastic Block Store (Amazon EBS) volume.
- Insufficient memory for your nodes.
- Upgrading OpenSearch Service to a newer version.
- Incompatibility between OpenSearch Dashboards and OpenSearch Service versions.
- A single-node cluster is running with a heavy load and no dedicated leader nodes. The dedicated leader node could also be unreachable.
Due to managed nature of service you won’t be able to perform a domain restart from your end. Please refer to below article for basic troubleshooting steps:
[+] https://repost.aws/knowledge-center/opensearch-dashboards-red-status
If you continue to experience such issues after performing basic troubleshooting, please reach out to support engineering for further assistance.
Relevant content
- asked 3 years ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- How do I resolve the "failed to obtain in-memory shard lock" exception in Amazon OpenSearch Service?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago