Hi All, A while ago I reported this issue, but back then I was running a single node cluser and though that may have been the issue. Yesterday I migrated to a triple node cluster configuration: 3 elasticsearch nodes (master and data nodes) 1 logstash 1 kibana 5 filebeats. Everything is running…

I tried, this time the file was missing. Then the cluster was restarted and when it came back the index was working like nothing happened. There is something very fishy here. I will continue trying to diagnose the FS

Unassigned Shard

Elastic Stack Elasticsearch

DavidTurner (David Turner) December 6, 2019, 1:55pm 3

I see a previous post from you about the same sort of issue here:

Did you try the same diagnosis steps as before? I.e. does ls /usr/share/elasticsearch/data/nodes/0/indices/50zRNBhxT3qdJpUdS4B47Q/0/index/ show a file called _1a4.fdt but ls /usr/share/elasticsearch/data/nodes/0/indices/50zRNBhxT3qdJpUdS4B47Q/0/index/_1a4.fdt reports No such file or directory? If so there's something fundamentally wrong with your filesystem again.

Topic		Replies	Views
Elasticseach failed shard allocation Elasticsearch	8	1353	May 28, 2021
Unassigned shards on cluster restart Elasticsearch	1	683	October 2, 2018
UNASSIGNED ALLOCATION_FAILED Elasticsearch	2	627	February 10, 2023
How to fix UNASSIGNED shard in Elasticsearch Elasticsearch	6	5412	July 5, 2017
Two unassigned shards as failed to create engine with error no such file exception Elasticsearch	4	691	April 22, 2019

Unassigned Shard

Related topics