# Shard Allocation awareness stopped working

**URL:** https://discuss.elastic.co/t/shard-allocation-awareness-stopped-working/215330
**Category:** Elasticsearch
**Created:** [January 16, 2020, 2:32pm UTC](https://discuss.elastic.co/t/shard-allocation-awareness-stopped-working/215330 "2020-01-16T14:32:41Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![74db36a597f21b891b3f](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/74db36a597f21b891b3f/32/45367_2.png) [@74db36a597f21b891b3f](https://discuss.elastic.co/u/74db36a597f21b891b3f)
#### Post date: [January 16, 2020, 2:32pm UTC](https://discuss.elastic.co/t/shard-allocation-awareness-stopped-working/215330/1 "2020-01-16T14:32:41Z")

</div>

Hello. I configured forced shard allocation awareness on my cluster as described here some time earlier. And it was working well.

But now I find out that some indices with one shard and one replica allocated on the nodes with same label.  
Nodes has approximately equal free space below 80% watermark. So I can't find another explanation of such cluster allocation behaviour.  
Need help please.

---

<div class="post-metadata">

### Author: ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [January 16, 2020, 2:45pm UTC](https://discuss.elastic.co/t/shard-allocation-awareness-stopped-working/215330/2 "2020-01-16T14:45:17Z")

</div>

> [@74db36a597f21b891b3f](#):
>
> I can't find another explanation of such cluster allocation behaviour.

I suggest [the cluster allocation explain API](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-allocation-explain.html) 🙂 If you ask it to explain the allocation of one of the shards that you think is allocated wrongly then you should get the information you need. Share it here if you need help interpreting it.

---

<div class="post-metadata">

### Author: ![74db36a597f21b891b3f](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/74db36a597f21b891b3f/32/45367_2.png) [@74db36a597f21b891b3f](https://discuss.elastic.co/u/74db36a597f21b891b3f)
#### Post date: [January 17, 2020, 8:39am UTC](https://discuss.elastic.co/t/shard-allocation-awareness-stopped-working/215330/3 "2020-01-17T08:39:45Z")

</div>

Found a root of problem. Not all master nodes had attribute enumeration in config.

---

<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: [February 14, 2020, 8:39am UTC](https://discuss.elastic.co/t/shard-allocation-awareness-stopped-working/215330/4 "2020-02-14T08:39:50Z")

</div>

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