Good question. Sorry to hear about your issues!
AWS recommends resolving the red cluster status first before reconfiguring your OpenSearch Service domain. Typically a red cluster status means 1 primary shard and the replicas are not allocated. OpenSearch will take snapshots but these fail when the red cluster status persists.
2 of the most common causes are failed cluster nodes and the process crashing from a heavy load. The following can help identify the issue:
- GET /_cluster/allocation/explain
- GET /_cat/indices?v
From that info, you can try the following:
- Delete the problematic index
- Restore a snapshot
- Delete documents from the index
- Change the index settings
- Reduce the number of replicas
- Delete other indices to free up disk space.
For failed cluster nodes or more complex issues that aren't solvable by the above, you can reach out to AWS Support for more help as detailed here: https://docs.aws.amazon.com/opensearch-service/latest/developerguide/handling-errors.html
ElasticSearch version change gets stuck in Amazon OpenSearch Serviceasked 4 months ago
Amazon OpenSearch Service Tutorialasked 24 days ago
R20210426-P2 software update - does that upgrade ElascticSearch version?Accepted Answerasked a year ago
Cannot upgrade OpenSearch service for unknown reasonAccepted Answerasked 9 months ago
Amazon OpenSearch Service tenant auto-switchingasked 16 days ago
Amazon Linux stuck at vulnerable 2.4.51 version, no update available?asked 9 months ago
Change OpenSearch Dashboard domain nameasked 3 months ago
Elasticache for Redis cluster service update got stuckasked 7 months ago
AWS OpenSearch Service got error after enable auto-tuneasked 4 months ago
What could I do when the amazon opensearch instance is stuck in update for more than a week?asked 9 months ago