- 最新
- 投票最多
- 评论最多
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
curl -XGET 'https://xx/_cat/indices?v'
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .kibana xx 1 1 2 0 18.7kb 9.3kb
green open book xx 5 0 52598 150 24.1mb 24.1mbcurl -XGET 'https://xx/_cluster/allocation/explain?pretty' "reason" : "unable to find any unassigned shards to explain [ClusterAllocationExplainRequest[useAnyUnassignedShard=true,includeYesDecisions?=false]"
For both suggested methods, they both seem normal at this moment, dunno why it's still stuck in processing
相关内容
AWS 官方已更新 3 年前- AWS 官方已更新 1 年前
- AWS 官方已更新 3 年前
Follow up on my question: I finially solved it by creating a new instance of same elastic search version. Then recover the snapshot from the old one to the new one and remove the old one (which was stuck in processing) It is fine to remove a processing elastic search instance at last. The only change is the name of the instance ( you might need to recreate it again to use back the old one's name)