I have a 2 node cluster with 1 shard per node and no replication. The cluster is used for logging and uses daily indexes. Normally everything runs fine but the index that was created a few days ago turned red half way through the day and stopped accepting data.
If a do a /_cluster/allocation/explain i get the following error explanation:
cannot allocate because allocation is not permitted to any of the nodes that hold an in-sync shard copy
Both nodes are otherwise running fine and accepting data on all other indices. Has anybody got an idea as to what is causing this and what I can do to fix it?
I have similar problem, too. My servers encountered HW crash and ES cluster has many unassigned shards.
GET /_cluster/allocation/explain
"details": "failed to create shard, failure FileSystemException[/data/elasticsearch/data/nodes/0/indices/35ByVBpBTdiFQ_TLgq4L2w/5/_state/state-1.st.tmp: Read-only file system]"
I use reroute API to fix those unassigned shards because I see the explanation as below
"explanation": "shard has exceeded the maximum number of retries [5] on failed allocation attempts - manually call [/_cluster/reroute?retry_failed=true] to retry
So, POST /_cluster/reroute?retry_failed=true may help you.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.