# Cluster doesn't respect routing.allocation.require.data\_type

**URL:** <https://discuss.elastic.co/t/cluster-doesnt-respect-routing-allocation-require-data-type/270700>\
**Category:** Elasticsearch\
**Created:** [April 20, 2021, 12:10pm UTC](https://discuss.elastic.co/t/cluster-doesnt-respect-routing-allocation-require-data-type/270700 "2021-04-20T12:10:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gorek](https://avatars.discourse-cdn.com/v4/letter/g/f08c70/32.png) [@gorek](https://discuss.elastic.co/u/gorek)\
**Post date:** [April 20, 2021, 12:10pm UTC](https://discuss.elastic.co/t/cluster-doesnt-respect-routing-allocation-require-data-type/270700/1 "2021-04-20T12:10:00Z")

</div>

Hi,

we have cluster with 2 nodes. Every node has set `data_type` attribute.  
One node has low disk watermark exceed.  
We prepared ILM policy to keep indices on one node for some time and after move it to another.  
Rarely I move some indices manually to another node by set index `routing.allocation.require.data_type` setting.

Few days ago one of node filled up disk because moving indices to another node stops working. When I manually set `routing.allocation.require.data_type` to value of second node data\_type parameter nothing happens (I can't see any relocating shards in `_cat/shards` results. `cluster/allocation/explain` also doesn't show anything).

Few months ago I move indices this way without problems.  
All (production) indices has 0 replicas so low disk watermark should not be a problem.

Have you any idea why indices doesn't move to another node?

Elastic version: 6.8.13

Thank you.

---

<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:** [April 20, 2021, 3:11pm UTC](https://discuss.elastic.co/t/cluster-doesnt-respect-routing-allocation-require-data-type/270700/2 "2021-04-20T15:11:59Z")

</div>

Cluster allocation explain is the best way to explain why a particular shard is allocated as it is. What do you mean it doesn't show anything? It will always say something about the target shard.

---

<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:** [May 18, 2021, 3:12pm UTC](https://discuss.elastic.co/t/cluster-doesnt-respect-routing-allocation-require-data-type/270700/3 "2021-05-18T15:12:40Z")

</div>

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