# ILM policy trigerring late

**URL:** <https://discuss.elastic.co/t/ilm-policy-trigerring-late/265436>\
**Category:** Elasticsearch\
**Created:** [February 25, 2021, 6:15am UTC](https://discuss.elastic.co/t/ilm-policy-trigerring-late/265436 "2021-02-25T06:15:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![maheshe](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@maheshe](https://discuss.elastic.co/u/maheshe)\
**Post date:** [February 25, 2021, 6:15am UTC](https://discuss.elastic.co/t/ilm-policy-trigerring-late/265436/1 "2021-02-25T06:15:04Z")

</div>

Hi : I am trying to dev test the ILM template by specifying the below...

The rollover happens after a few minutes and after it reaches like 750KB instead of 10 KB as mentioned in ILM. Why is it not rolling over as soon as it reaches 10kb itself

----------------------ILM Policy:---------------------------------------------------

```auto
{
  "PolicyILMTester" : {
    "version" : 3,
    "modified_date" : "2021-02-25T05:44:39.321Z",
    "policy" : {
      "phases" : {
        "hot" : {
          "min_age" : "0ms",
          "actions" : {
            "rollover" : {
              "max_size" : "10kb",
              "max_age" : "1m"
            },
            "set_priority" : {
              "priority" : 100
            }
          }
        }
      }
    }
  }
}

```

-------------------------------------------Index template & Index creation- bootstrapped-----------------------------

```auto
PUT _index_template/eventaudit_template
{
  "index_patterns": ["event.intune-api_data-*"],                 
  "template": {
    "settings": {
      "number_of_replicas": 0,
      "index.lifecycle.name": "PolicyILMTester",      
      "index.lifecycle.rollover_alias": "event.intune-api_data"    
    }
  }
}

PUT event.intune-api_data-2021-02-24-000001
{
  "aliases": {
    "event.intune-api_data": {
      "is_write_index": true
    }
  }
}

```

---

<div class="post-metadata">

**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\
**Post date:** [February 25, 2021, 6:21am UTC](https://discuss.elastic.co/t/ilm-policy-trigerring-late/265436/2 "2021-02-25T06:21:43Z")

</div>

Hello Mahesh,

ElasticSearch has a setting `indices.lifecycle.poll_interval` (see [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-settings.html) for details) which describes how often ElasticSearch for indices that meet the ILM criterias. The default value is 10 minutes. Although this overruns your limit in your test this should be fine for most usecases in reality.

Best regards  
Wolfram

---

<div class="post-metadata">

**Author:** ![maheshe](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@maheshe](https://discuss.elastic.co/u/maheshe)\
**Post date:** [February 25, 2021, 5:27pm UTC](https://discuss.elastic.co/t/ilm-policy-trigerring-late/265436/3 "2021-02-25T17:27:19Z")

</div>

Thank you @Wolfram_Haussig . This clarifies.

---

<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:** [March 25, 2021, 5:27pm UTC](https://discuss.elastic.co/t/ilm-policy-trigerring-late/265436/4 "2021-03-25T17:27:23Z")

</div>

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