# Index.ttl.disable\_purge flag not working?

**URL:** <https://discuss.elastic.co/t/index-ttl-disable-purge-flag-not-working/8057>\
**Category:** Elasticsearch\
**Created:** [June 12, 2012, 11:52am UTC](https://discuss.elastic.co/t/index-ttl-disable-purge-flag-not-working/8057 "2012-06-12T11:52:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stefan\_Pi](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@Stefan\_Pi](https://discuss.elastic.co/u/Stefan_Pi)\
**Post date:** [June 12, 2012, 11:52am UTC](https://discuss.elastic.co/t/index-ttl-disable-purge-flag-not-working/8057/1 "2012-06-12T11:52:15Z")

</div>

Hi everybody,

I'm using ES 0.19.4. I tried to disable the deletion process for documents  
of an existing index that was initially created with a TTL (The TTL  
deletion is working fine). I've tried to update the index using the  
index.ttl.disable\_purge flag as described here:  
[http://www.elasticsearch.org/guide/reference/api/admin-indices-update-settings.html](http://www.elasticsearch.org/guide/reference/api/admin-indices-update-settings.html)  
but it seems not to work:

curl -XPUT '://\_settings' -d '{"index" :  
{"index.ttl.disable\_purge" : true} }'

This was written to the log file of the node after doing the above call:

[WARN][cluster.metadata] [] [] ignoring non dynamic index  
level settings for open indices: [index.index.ttl.disable\_purge]

I also tried the call with a slight flag name variation removing the  
"index" at the beginning of the flag:

curl -XPUT '://\_settings' -d '{"index" :  
{"ttl.disable\_purge" : true} }'

but also without success:

[WARN][cluster.metadata] [] [] ignoring non dynamic index  
level settings for open indices: [index.ttl.disable\_purge]

I understand that non-dynamic settings can not be changed when the index  
was already created but according to the documentaton (above link) this  
should be a dynamic setting. Am I doing something wrong? Any help would be  
much appreciated!

Thanks,  
Stefan

---

<div class="post-metadata">

**Author:** ![Benjamin\_Deveze](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benjamin_deveze/32/1577_2.png) [@Benjamin\_Deveze](https://discuss.elastic.co/u/Benjamin_Deveze)\
**Post date:** [June 12, 2012, 1:34pm UTC](https://discuss.elastic.co/t/index-ttl-disable-purge-flag-not-working/8057/2 "2012-06-12T13:34:19Z")

</div>

You are right it is a bug, expect it to be fixed tonight.

Thanks

On Tue, Jun 12, 2012 at 1:52 PM, Stefan Pi [sp@media-metrics.de](mailto:sp@media-metrics.de) wrote:

> Hi everybody,
> 
> I'm using ES 0.19.4. I tried to disable the deletion process for documents  
> of an existing index that was initially created with a TTL (The TTL deletion  
> is working fine). I've tried to update the index using the  
> index.ttl.disable\_purge flag as described here:  
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-update-settings.html)  
> but it seems not to work:
> 
> curl -XPUT '://\_settings' -d '{"index" :  
> {"index.ttl.disable\_purge" : true} }'
> 
> This was written to the log file of the node after doing the above call:
> 
> [WARN][cluster.metadata] [] [] ignoring non dynamic index  
> level settings for open indices: [index.index.ttl.disable\_purge]
> 
> I also tried the call with a slight flag name variation removing the "index"  
> at the beginning of the flag:
> 
> curl -XPUT '://\_settings' -d '{"index" :  
> {"ttl.disable\_purge" : true} }'
> 
> but also without success:
> 
> [WARN][cluster.metadata] [] [] ignoring non dynamic index  
> level settings for open indices: [index.ttl.disable\_purge]
> 
> I understand that non-dynamic settings can not be changed when the index was  
> already created but according to the documentaton (above link) this should  
> be a dynamic setting. Am I doing something wrong? Any help would be much  
> appreciated!
> 
> Thanks,  
> Stefan

--  
Benjamin DEVEZE

---

<div class="post-metadata">

**Author:** ![Stefan\_Pi](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@Stefan\_Pi](https://discuss.elastic.co/u/Stefan_Pi)\
**Post date:** [June 12, 2012, 2:21pm UTC](https://discuss.elastic.co/t/index-ttl-disable-purge-flag-not-working/8057/3 "2012-06-12T14:21:08Z")

</div>

Great! Where will it be fixed? Do I have to download and build the master  
or will it be patched into 0.19.4?

Thanks, Stefan

---

<div class="post-metadata">

**Author:** ![Benjamin\_Deveze](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benjamin_deveze/32/1577_2.png) [@Benjamin\_Deveze](https://discuss.elastic.co/u/Benjamin_Deveze)\
**Post date:** [June 12, 2012, 9:56pm UTC](https://discuss.elastic.co/t/index-ttl-disable-purge-flag-not-working/8057/4 "2012-06-12T21:56:52Z")

</div>

Ok it has been fixed in 0.19 branch and master. So you can use the  
master or wait for 0.19.5 I guess.

On Tue, Jun 12, 2012 at 4:21 PM, Stefan Pi [sp@media-metrics.de](mailto:sp@media-metrics.de) wrote:

> Great! Where will it be fixed? Do I have to download and build the master or  
> will it be patched into 0.19.4?
> 
> Thanks, Stefan

--  
Benjamin DEVEZE

---

<div class="post-metadata">

**Author:** ![Stefan\_Pi](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@Stefan\_Pi](https://discuss.elastic.co/u/Stefan_Pi)\
**Post date:** [June 13, 2012, 10:25am UTC](https://discuss.elastic.co/t/index-ttl-disable-purge-flag-not-working/8057/5 "2012-06-13T10:25:19Z")

</div>

Thank you very much!

---

<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:** [July 6, 2017, 3:24am UTC](https://discuss.elastic.co/t/index-ttl-disable-purge-flag-not-working/8057/6 "2017-07-06T03:24:39Z")

</div>


