# ElasticSearch Service: 2 of 15 shards failed **URL:** \ **Category:** Elasticsearch\ **Created:** [October 28, 2019, 3:23pm UTC](https://discuss.elastic.co/t/elasticsearch-service-2-of-15-shards-failed/205505 "2019-10-28T15:23:42Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![AndresL](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andresl/32/54070_2.png) [@AndresL](https://discuss.elastic.co/u/AndresL)\ **Post date:** [October 28, 2019, 3:23pm UTC](https://discuss.elastic.co/t/elasticsearch-service-2-of-15-shards-failed/205505/1 "2019-10-28T15:23:42Z")
Hi, In a ESS cluster, from kibana dashboard i can see the error " 2 of 15 shards failed how can i debuig this problem? i have been checking in system logs like .monitoring or .kibana, and i cant find the reason. Version is 7.3 ---
**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\ **Post date:** [October 28, 2019, 4:24pm UTC](https://discuss.elastic.co/t/elasticsearch-service-2-of-15-shards-failed/205505/2 "2019-10-28T16:24:21Z")
I'm moving this to the Elasticsearch forum since it doesn't seem cloud specific - note that Elasticsearch Service doesn't have a discuss forum, instead we ask that people request support here: [https://cloud.elastic.co/help](https://cloud.elastic.co/help)) I would suggest `_cat/shards` and `_cluster/allocation/explain` as 2 good APIs to provide information about why shards are not allocating properly. The elasticsearch logs (accessible from ES) are also useful ---
**Author:** ![AndresL](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andresl/32/54070_2.png) [@AndresL](https://discuss.elastic.co/u/AndresL)\ **Post date:** [October 29, 2019, 11:48am UTC](https://discuss.elastic.co/t/elasticsearch-service-2-of-15-shards-failed/205505/3 "2019-10-29T11:48:04Z")
Hi Alex, using \_cat/shards i can see all the index in status "Started" (system index, filebeat, etc). Using `_cluster/allocation/explain` for one specific index, i got this answer: > **Summary** > > "index" : "filebeat-development-7.3.0-2019.10.28", > "shard" : 0, > "primary" : true, > "current\_state" : "started", > "current\_node" : { > "id" : "roBcUoF0SJGixpfEwq2PrQ", > "name" : "instance-0000000001", > "transport\_address" : "10.46.24.5:19095", > "attributes" : { > "logical\_availability\_zone" : "zone-1", > "server\_name" : "instance-0000000001.509b35a803234a588f5da5e49f9a1e3c", > "availability\_zone" : "westeurope-1", > "xpack.installed" : "true", > "region" : "unknown-region", > "instance\_configuration" : "azure.data.highio.l32sv2" > }, > "weight\_ranking" : 3 > }, > "can\_remain\_on\_current\_node" : "yes", > "can\_rebalance\_cluster" : "yes", > "can\_rebalance\_to\_other\_node" : "no", > "rebalance\_explanation" : "cannot rebalance as no target node exists that can both allocate this shard and improve the cluster balance", > "node\_allocation\_decisions" : [ > { > "node\_id" : "KWBh3OBrQWWKWAGSmnU8cg", > "node\_name" : "instance-0000000005", > "transport\_address" : "10.46.24.45:19337", > "node\_attributes" : { > "logical\_availability\_zone" : "zone-1", > "server\_name" : "instance-0000000005.509b35a803234a588f5da5e49f9a1e3c", > "availability\_zone" : "westeurope-1", > "xpack.installed" : "true", > "region" : "unknown-region", > "instance\_configuration" : "azure.data.highstorage.e16sv3" > }, > "node\_decision" : "no", > "weight\_ranking" : 1, > "deciders" : [ > { > "decider" : "filter", > "decision" : "NO", > "explanation" : """node does not match index setting [index.routing.allocation.include] filters [instance\_configuration:"azure.data.highio.l32sv2"]""" > } > ] > }, > { > "node\_id" : "8eUTEMX\_Q0aoHJ1nyQfKJQ", > "node\_name" : "instance-0000000006", > "transport\_address" : "10.46.24.52:19824", > "node\_attributes" : { > "logical\_availability\_zone" : "zone-0", > "server\_name" : "instance-0000000006.509b35a803234a588f5da5e49f9a1e3c", > "availability\_zone" : "westeurope-3", > "xpack.installed" : "true", > "region" : "unknown-region", > "instance\_configuration" : "azure.data.highstorage.e16sv3" > }, > "node\_decision" : "no", > "weight\_ranking" : 2, > "deciders" : [ > { > "decider" : "filter", > "decision" : "NO", > "explanation" : """node does not match index setting [index.routing.allocation.include] filters [instance\_configuration:"azure.data.highio.l32sv2"]""" > } > ] > }, > { > "node\_id" : "O\_1rItnVQW-sbRsjWmRdFw", > "node\_name" : "instance-0000000007", > "transport\_address" : "10.46.24.17:19878", > "node\_attributes" : { > "logical\_availability\_zone" : "zone-0", > "server\_name" : "instance-0000000007.509b35a803234a588f5da5e49f9a1e3c", > "availability\_zone" : "westeurope-3", > "xpack.installed" : "true", > "region" : "unknown-region", > "instance\_configuration" : "azure.data.highio.l32sv2" > }, > "node\_decision" : "no", > "weight\_ranking" : 3, > "deciders" : [ > { > "decider" : "same\_shard", > "decision" : "NO", > "explanation" : "the shard cannot be allocated to the same node on which a copy of the shard already exists [[filebeat-development-7.3.0-2019.10.28][0], node[O\_1rItnVQW-sbRsjWmRdFw], [R], s[STARTED], a[id=BdNfo8jrSO-CqqbUHGzG7Q]]" > } > ] > } > ] > } ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 12, 2019, 11:48am UTC](https://discuss.elastic.co/t/elasticsearch-service-2-of-15-shards-failed/205505/4 "2019-11-12T11:48:06Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.