Suddenly the count operation on an index returned a few million less results than usual. Looking at application logs I see stacktraces when trying to add a new document. File "/myapp/MetaControl/MetaController.py", line 442, in save_av_analysis self.av_db.index(index="av_index_two", doc…

The shard cannot be allocated to the same node on which a copy of the shard already exists

DavidTurner (David Turner) May 18, 2020, 6:21pm 2

This is a replica, but you only have one node, so of course no replicas can be allocated. You should set number_of_replicas: 0 on all your indices.

Shards failed in Network screen

Topic		Replies	Views
The shard cannot be allocated to the same node on which a copy of the shard already exist Elasticsearch	1	1269	May 8, 2020
Shard cannot be allocated to the same node on which a copy of the shard already exists Elasticsearch	1	1964	November 22, 2019
Cannot allocate because a previous copy of the primary shard existed but can no longer be found on the nodes in the cluster Elasticsearch	9	15869	September 15, 2020
Shards are not allocating to available node Elasticsearch	2	1227	October 19, 2018
1 index having two shards went unassigned, when we do the cluster explain we received below response. Request you to assist on this issue Elasticsearch	1	149	November 7, 2023