# ILM not running on Elastic Cloud

**URL:** <https://discuss.elastic.co/t/ilm-not-running-on-elastic-cloud/196102>\
**Category:** Elasticsearch\
**Created:** [August 21, 2019, 12:13pm UTC](https://discuss.elastic.co/t/ilm-not-running-on-elastic-cloud/196102 "2019-08-21T12:13:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![norgro2601](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/norgro2601/32/33292_2.png) [@norgro2601](https://discuss.elastic.co/u/norgro2601)\
**Post date:** [August 21, 2019, 12:13pm UTC](https://discuss.elastic.co/t/ilm-not-running-on-elastic-cloud/196102/1 "2019-08-21T12:13:09Z")

</div>

Hi,

I've migrated a cluster to a new cluster based on the hot/warm template on the Elastic Cloud an restored all indices from the old cluster to the new cluster.  
Now I've noticed, that ILM is not running on any of the indices.  
I've stopped ILM and started it again, no change.  
I've removed the policy and added it again on the same index, nothing happens, no action is done.  
All indices show no Errors on the ILM/explain function.  
I've created a new index with beats, but also nothing happens on that index.

I have no more ideas, what the problem could be, any recommendations ?

Thanks in advance.

Best regards,  
Norbert

---

<div class="post-metadata">

**Author:** ![gbrown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gbrown/32/34482_2.png) [@gbrown](https://discuss.elastic.co/u/gbrown)\
**Post date:** [August 21, 2019, 4:45pm UTC](https://discuss.elastic.co/t/ilm-not-running-on-elastic-cloud/196102/2 "2019-08-21T16:45:46Z")

</div>

Can you post the output of `GET */_ilm/explain` please, as well as one of the policies in use?

What are you expecting to see ILM do that it hasn't done?

---

<div class="post-metadata">

**Author:** ![norgro2601](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/norgro2601/32/33292_2.png) [@norgro2601](https://discuss.elastic.co/u/norgro2601)\
**Post date:** [August 22, 2019, 5:46am UTC](https://discuss.elastic.co/t/ilm-not-running-on-elastic-cloud/196102/3 "2019-08-22T05:46:30Z")

</div>

Hi Gordon,

I've found my problem.

There was one lifecycle policy definition missing for auditbeat-7.2.0 indices, I've restored from the old cluster. I've created the policy this morning, and immedialtely everything works as expected.

But as a programmer, I like to ask the question, why one missing policy stops all processing. I would expect, that only the indices, which use the missing policy, are skipped from processing, but not the whole processing at all stops. There should be an error handling that deals with "simple" errors like this, shouldn't it?

Best regards,  
Norbert

---

<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 19, 2019, 5:46am UTC](https://discuss.elastic.co/t/ilm-not-running-on-elastic-cloud/196102/4 "2019-09-19T05:46:31Z")

</div>

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