# Lifecycle policies don't work **URL:** \ **Category:** Elasticsearch\ **Tags:** ilm-index-lifecycle-management\ **Created:** [June 17, 2021, 5:03am UTC](https://discuss.elastic.co/t/lifecycle-policies-dont-work/276218 "2021-06-17T05:03:12Z")\ **Posts on this page:** 1\ **Showing post:** 13
**Author:** ![Cris\_Da\_Rocha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cris_da_rocha/32/45598_2.png) [@Cris\_Da\_Rocha](https://discuss.elastic.co/u/Cris_Da_Rocha)\ **Post date:** [June 17, 2021, 6:52pm UTC](https://discuss.elastic.co/t/lifecycle-policies-dont-work/276218/13 "2021-06-17T18:52:24Z")
@Sjaak01 ILM uses a [poll interval](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-settings.html) of 10 minutes (`indices.lifecycle.poll_interval`) which defaults to 10 minutes. The times in the phases are expected to be (considerably) larger than that, as @stephenb said. Your rollover with 1m and deletion with 5m is not helping that and could cause issues. We don't recommend changing this value for production, but for a test you could set it to 1 minute. Make your rollover be 2 or 3 minutes and your deletion 5 minutes. Also your [Logstash output](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html#plugins-outputs-elasticsearch-ilm) is pointing to the ILM settings AND to the index name. So there might be a conflict, or simply the ILM settings are being ignored, making ingestion always happen in `v2-testdiag-000001`, not in the alias, which should change after rollover. Remove the index name in the test. Logstash will create the index with the proper name and policy and actually write to the rollover alias, not to the first index as you specified. --- _[View the full topic](https://discuss.elastic.co/t/lifecycle-policies-dont-work/276218)._