# ES Unassigned shards number of allocated shards found \< required number

**URL:** <https://discuss.elastic.co/t/es-unassigned-shards-number-of-allocated-shards-found-required-number/146912>\
**Category:** Elasticsearch\
**Created:** [August 31, 2018, 8:06pm UTC](https://discuss.elastic.co/t/es-unassigned-shards-number-of-allocated-shards-found-required-number/146912 "2018-08-31T20:06:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![UDixit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/udixit/32/53219_2.png) [@UDixit](https://discuss.elastic.co/u/UDixit)\
**Post date:** [August 31, 2018, 8:06pm UTC](https://discuss.elastic.co/t/es-unassigned-shards-number-of-allocated-shards-found-required-number/146912/1 "2018-08-31T20:06:15Z")

</div>

In a 3 node cluster (all nodes being master eligible), the master left the cluster and then rejoined after an hour. Soon, all primary and secondary shards(shard 9) became unassigned for an index.

I am also seeing the following logs from gateway.local: [index\_name][9]: not allocating, number\_of\_allocated\_shards\_found [1], required\_number [2]

As per \_cluster/health API all primary and secondary shards for shard 9 are unassigned.

Why is there such a mismatch in the logs and the cluster health output? As per [gateway.local] logs, 1 shards is allocated, but the \_custer/health API indicates that all primary and secondary shards are unassigned.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 28, 2018, 8:06pm UTC](https://discuss.elastic.co/t/es-unassigned-shards-number-of-allocated-shards-found-required-number/146912/2 "2018-09-28T20:06:21Z")

</div>

Closed on September 28, 2018, 8:06pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.