Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

OpenSearch domain stuck in red status

0

Hi everyone,

Our OpenSearch Service domain experienced a quorum loss, which caused it to enter a read-only state.

Here’s what’s happening:

  • The cluster status is red
  • Authentication is failing (we can’t log in to the dashboard or access the API)

After carefully reviewing the AWS troubleshooting guidelines for red cluster status, we identified that the issue is related to shard allocation, and further action is required on our side. However, we’re currently unable to log in or call any API actions to address the issue.

Yesterday, we added additional data nodes to the cluster, but the stack update has been stuck at "Processing updates – 60%" for almost a full day now.

What can we do next to mitigate this issue? Any guidance or help would be greatly appreciated.

Thank you!

Topics
Analytics
Tags
Amazon OpenSearch Service
Language
English
asked 10 months ago144 views
1 Answer
0

If you can’t access the domain at all, no dashboard, no API, it’s likely the cluster state is too far degraded for OpenSearch to self-recover, especially after quorum loss. Since you've already added nodes and the update is stuck at 60%, I’d suggest raising a support case with AWS immediately and marking it as production-impacting. At this point, only AWS can force a domain recovery (by promoting replicas to primaries, reindexing from snapshots, or restoring a healthy cluster state manually). If you have daily snapshots enabled, AWS support may also help spin up a new domain from the last healthy snapshot while you troubleshoot the stuck one.

answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content