# PUT ILM Policy immediately return "acknowledged": false

**URL:** <https://discuss.elastic.co/t/put-ilm-policy-immediately-return-acknowledged-false/190885>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [July 17, 2019, 6:46am UTC](https://discuss.elastic.co/t/put-ilm-policy-immediately-return-acknowledged-false/190885 "2019-07-17T06:46:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tami](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tami/32/45312_2.png) [@tami](https://discuss.elastic.co/u/tami)\
**Post date:** [July 17, 2019, 6:46am UTC](https://discuss.elastic.co/t/put-ilm-policy-immediately-return-acknowledged-false/190885/1 "2019-07-17T06:46:30Z")

</div>

We are using elasticsearch 6.7.2 deployed on k8s with a configuration of 3 master, 4 data, 2 client nodes.

When setting some ILM Policies, I am seeing that it is immediately returning with "acknowledged": false. My understanding is that this should only happen if there is a timeout on one of the nodes, and that the acknowledged: false is not necessarily an error, but just indicates that the operation could not complete before the timeout.

I am a bit confused by this as I thought the default timeout was either 10s or 30s, so the fact that it returns false immediately is confusing to me. My code relies on this operation being completed before trying to create any indices to make sure the policy is successfully updated. When i was running this with a different configuration (3 master, 2 data, 2 client), it would always return acknowledged as true.

My question is, why would this be returning acknowledged: false so quickly, and how can I make this operation wait for acknowledged: true before returning.

---

<div class="post-metadata">

**Author:** ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)\
**Post date:** [July 17, 2019, 3:33pm UTC](https://discuss.elastic.co/t/put-ilm-policy-immediately-return-acknowledged-false/190885/2 "2019-07-17T15:33:16Z")

</div>

> [@tami](#):
>
> My question is, why would this be returning acknowledged: false so quickly, and how can I make this operation wait for acknowledged: true before returning.

That is a good question indeed, do you see any indication in the logs about why the operation may be failing? Perhaps an error or stacktrace in the logs?

---

<div class="post-metadata">

**Author:** ![tami](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tami/32/45312_2.png) [@tami](https://discuss.elastic.co/u/tami)\
**Post date:** [July 17, 2019, 6:42pm UTC](https://discuss.elastic.co/t/put-ilm-policy-immediately-return-acknowledged-false/190885/3 "2019-07-17T18:42:18Z")

</div>

Thanks.

I don't see any information in the logs of the client, master, or data nodes about this request or about any failure. All i get in "acknowledged": false. And the PUT operation seems to be succeeding, as an immediate GET request on the policy shows that it updated, has a new modified timestamp and version number.

---

<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:** [August 14, 2019, 6:42pm UTC](https://discuss.elastic.co/t/put-ilm-policy-immediately-return-acknowledged-false/190885/4 "2019-08-14T18:42:25Z")

</div>

Closed on August 14, 2019, 6:42pm UTC

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