# Elastic ILM does not work as expected after upgrading Elastic
**URL:** https://discuss.elastic.co/t/elastic-ilm-does-not-work-as-expected-after-upgrading-elastic/261554
**Category:** Beats
**Tags:** ilm-index-lifecycle-management, filebeat
**Created:** [January 19, 2021, 2:06pm UTC](https://discuss.elastic.co/t/elastic-ilm-does-not-work-as-expected-after-upgrading-elastic/261554 "2021-01-19T14:06:45Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Ali\_Nazemian](https://discuss.elastic.co/u/Ali_Nazemian)
#### Post date: [January 19, 2021, 2:06pm UTC](https://discuss.elastic.co/t/elastic-ilm-does-not-work-as-expected-after-upgrading-elastic/261554/1 "2021-01-19T14:06:45Z")
After I have upgraded my Elasticsearch cluster from 7.9 to 7.10.1 my ILM for filebeat does not work as expected. I can see that the corresponding indices are being marked as Warm when I check the index management, but I noticed that they are still stored on hot nodes. After I did a bit investigation, I noticed that for "warm" indices still the value for `index.routing.allocation.require.data` is "hot". If I manually update the index by running the following request it works and it's moved to the "warm" node, but I'm not sure why it keeps producing the "warm" indices with an incorrect routing value.
```
PUT filebeat-2021.01.13*/_settings
{
"index.routing.allocation.require.data": "warm"
}
```
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [January 25, 2021, 12:12am UTC](https://discuss.elastic.co/t/elastic-ilm-does-not-work-as-expected-after-upgrading-elastic/261554/2 "2021-01-25T00:12:57Z")
Sharing your policy would be helpful 🙂
---
### Author:  [@Ali\_Nazemian](https://discuss.elastic.co/u/Ali_Nazemian)
#### Post date: [January 25, 2021, 12:36am UTC](https://discuss.elastic.co/t/elastic-ilm-does-not-work-as-expected-after-upgrading-elastic/261554/3 "2021-01-25T00:36:09Z")
The policy seems entirely fine and it in fact works as expected on another cluster:
```
{
"policy": {
"phases": {
"hot": {
"min_age": "0ms",
"actions": {
"rollover": {
"max_size": "10gb",
"max_age": "1d"
}
}
},
"warm": {
"min_age": "3d",
"actions": {
"allocate": {
"include": {},
"exclude": {},
"require": {
"data": "warm"
}
},
"shrink": {
"number_of_shards": 1
}
}
},
"delete": {
"min_age": "30d",
"actions": {
"delete": {
"delete_searchable_snapshot": true
}
}
}
}
}
}
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 22, 2021, 2:36am UTC](https://discuss.elastic.co/t/elastic-ilm-does-not-work-as-expected-after-upgrading-elastic/261554/4 "2021-02-22T02:36:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.