# Index Routing Allocation does not move Index
**URL:** https://discuss.elastic.co/t/index-routing-allocation-does-not-move-index/157503
**Category:** Elasticsearch
**Created:** [November 20, 2018, 9:02am UTC](https://discuss.elastic.co/t/index-routing-allocation-does-not-move-index/157503 "2018-11-20T09:02:52Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@cduong](https://discuss.elastic.co/u/cduong)
#### Post date: [November 20, 2018, 9:02am UTC](https://discuss.elastic.co/t/index-routing-allocation-does-not-move-index/157503/1 "2018-11-20T09:02:52Z")
Hi,
I'm using Elastic Cloud. I created the cluster with Hot Warm arch for timeseries. I applied the Index Curation in which it will move index after 1 day from Hot node to the Warm node.
After 2/3 days, I checked the index's setting has been updated to be routed to the Warm node.
```auto
"index.routing.allocation.include.instance_configuration": "aws.data.highstorage.d2",
```
However, the index still stay in Hot node. I don't why it does not work. The Warm node is mostly 0% disk usage, while the Hot node is 30% disk usage.
The full index's setting is
```json
{
"index.blocks.read_only_allow_delete": "false",
"index.priority": "1",
"index.query.default_field": [
"*"
],
"index.refresh_interval": "1s",
"index.write.wait_for_active_shards": "1",
"index.routing.allocation.include.instance_configuration": "aws.data.highstorage.d2",
"index.number_of_replicas": "1"
}
```
---
### Author:  [@val](https://discuss.elastic.co/u/val)
#### Post date: [November 20, 2018, 9:08am UTC](https://discuss.elastic.co/t/index-routing-allocation-does-not-move-index/157503/2 "2018-11-20T09:08:01Z")
Please show what you get when running the following command (make sure to replace `your-index` by the real index name):
```
GET your-index/_settings?include_defaults=true&filter_path= **.routing.**
```
---
### Author:  [@cduong](https://discuss.elastic.co/u/cduong)
#### Post date: [November 20, 2018, 9:51am UTC](https://discuss.elastic.co/t/index-routing-allocation-does-not-move-index/157503/3 "2018-11-20T09:51:35Z")
This is the output
```json
{
"settings": {
"index": {
"routing": {
"allocation": {
"include": {
"instance_configuration": "aws.data.highstorage.d2"
}
}
}
}
},
"defaults": {
"index": {
"routing": {
"rebalance": {
"enable": "all"
},
"allocation": {
"enable": "all",
"total_shards_per_node": "-1"
}
}
}
}
}
```
---
### Author:  [@mattsdevop](https://discuss.elastic.co/u/mattsdevop)
#### Post date: [November 20, 2018, 7:56pm UTC](https://discuss.elastic.co/t/index-routing-allocation-does-not-move-index/157503/4 "2018-11-20T19:56:39Z")
Edit: Please ignore my post. My resolution was completely different.
Due to the data being on the hot and warm nodes, it was necessary for me to take it down to 1 Replica before allocation. After which, it worked as expected.
Edit2: Can I just say how much I appreciated seeing "wait\_for\_it" as Curator debug output? 😆
Original post:
> I'm using "require" and am experiencing the same behavior.
>
> ```auto
> index.routing.allocation.require.{attribute}
>
> ```
>
> Curator config:
>
> ```auto
> actions:
> 1:
> action: allocation
> description: >-
> Move indices older than 8 days (based on index name), for production
> prefixed indices to warm, data-only node for archival.
> options:
> key: box_type
> value: warm
> allocation_type: require
> wait_for_completion: True
> ignore_empty_list: True
> timeout_override:
> continue_if_exception: False
> disable_action: False
> filters:
> - filtertype: pattern
> kind: prefix
> value: 'customer-environment-'
> - filtertype: age
> source: name
> direction: older
> timestring: '%Y.%m.%d'
> unit: days
> unit_count: 8
>
> ```
>
> ```auto
> {
> "customer-environment-2018.11.02": {
> "settings": {
> "index": {
> "routing": {
> "allocation": {
> "require": {
> "box_type": "warm"
> }
> }
> }
> }
> }
> }
> }
>
> ```
>
> However, when viewing the index within Monitoring in Kibana, it still shows on the hot and warm node:
> 
> 
---
### Author:  [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [November 20, 2018, 8:10pm UTC](https://discuss.elastic.co/t/index-routing-allocation-does-not-move-index/157503/5 "2018-11-20T20:10:23Z")
I recommend looking at the elasticsearch logs.
Are you certain that the appropriate node tag is configured in the `elasticsearch.yml` file and the node was restarted after that setting was added?
---
### Author:  [@cduong](https://discuss.elastic.co/u/cduong)
#### Post date: [November 22, 2018, 8:46am UTC](https://discuss.elastic.co/t/index-routing-allocation-does-not-move-index/157503/6 "2018-11-22T08:46:41Z")
Hi,
I had noticed some weird attributes of Cloud ES nodes. There is an inconsistent in attributes (one node zone a, can belong to 2 logical zones), means the ES Allocation awareness would be in tight state, which the shards cannot even move to another nodes. Because it either change AZ, or logical AZ.
This is the inconsistent attributes
```auto
instance-0000000005 logical_availability_zone zone-0
instance-0000000005 availability_zone ap-southeast-1b
instance-0000000005 xpack.installed true
instance-0000000005 region ap-southeast-1
instance-0000000005 instance_configuration aws.data.highstorage.d2
nstance-0000000006 logical_availability_zone zone-1
instance-0000000006 availability_zone ap-southeast-1a
instance-0000000006 xpack.installed true
instance-0000000006 region ap-southeast-1
instance-0000000006 instance_configuration aws.data.highstorage.d2
instance-0000000000 logical_availability_zone zone-0
instance-0000000000 availability_zone ap-southeast-1a
instance-0000000000 xpack.installed true
instance-0000000000 region ap-southeast-1
instance-0000000000 instance_configuration aws.data.highio.i3
instance-0000000001 logical_availability_zone zone-1
instance-0000000001 availability_zone ap-southeast-1b
instance-0000000001 xpack.installed true
instance-0000000001 region ap-southeast-1
instance-0000000001 instance_configuration aws.data.highio.i3
```
However, today it seems to be fixed by Elastic team. The attributes is consistent now.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 20, 2018, 8:46am UTC](https://discuss.elastic.co/t/index-routing-allocation-does-not-move-index/157503/7 "2018-12-20T08:46:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.