# Use of index.merge.policy.reclaim\_deletes\_weight in 2.3

**URL:** <https://discuss.elastic.co/t/use-of-index-merge-policy-reclaim-deletes-weight-in-2-3/73746>\
**Category:** Elasticsearch\
**Created:** [February 2, 2017, 7:45pm UTC](https://discuss.elastic.co/t/use-of-index-merge-policy-reclaim-deletes-weight-in-2-3/73746 "2017-02-02T19:45:19Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![kadey](https://avatars.discourse-cdn.com/v4/letter/k/df705f/32.png) [@kadey](https://discuss.elastic.co/u/kadey)\
**Post date:** [February 2, 2017, 7:45pm UTC](https://discuss.elastic.co/t/use-of-index-merge-policy-reclaim-deletes-weight-in-2-3/73746/1 "2017-02-02T19:45:19Z")

</div>

Does the index.merge.policy.reclaim\_deletes\_weight configuration parameter still exist in 2.3.3?

I could not find it in the documentation. The last version that contains a reference to this is 1.7.

---

<div class="post-metadata">

**Author:** ![abeyad](https://avatars.discourse-cdn.com/v4/letter/a/278dde/32.png) [@abeyad](https://discuss.elastic.co/u/abeyad)\
**Post date:** [February 2, 2017, 8:27pm UTC](https://discuss.elastic.co/t/use-of-index-merge-policy-reclaim-deletes-weight-in-2-3/73746/2 "2017-02-02T20:27:11Z")

</div>

The parameter exists in 2.x, though one must be careful when changing it, see this blog post: [https://www.elastic.co/blog/lucenes-handling-of-deleted-documents](https://www.elastic.co/blog/lucenes-handling-of-deleted-documents)

---

<div class="post-metadata">

**Author:** ![kadey](https://avatars.discourse-cdn.com/v4/letter/k/df705f/32.png) [@kadey](https://discuss.elastic.co/u/kadey)\
**Post date:** [February 3, 2017, 1:22pm UTC](https://discuss.elastic.co/t/use-of-index-merge-policy-reclaim-deletes-weight-in-2-3/73746/3 "2017-02-03T13:22:54Z")

</div>

I presume this needs to be set on each node, and then the whole cluster restarted?

---

<div class="post-metadata">

**Author:** ![abeyad](https://avatars.discourse-cdn.com/v4/letter/a/278dde/32.png) [@abeyad](https://discuss.elastic.co/u/abeyad)\
**Post date:** [February 3, 2017, 2:23pm UTC](https://discuss.elastic.co/t/use-of-index-merge-policy-reclaim-deletes-weight-in-2-3/73746/4 "2017-02-03T14:23:34Z")

</div>

No, you just need to update the index settings to set this parameter, and it will propagate to all nodes (it will be stored in the cluster state). No restart is needed.

---

<div class="post-metadata">

**Author:** ![kadey](https://avatars.discourse-cdn.com/v4/letter/k/df705f/32.png) [@kadey](https://discuss.elastic.co/u/kadey)\
**Post date:** [February 3, 2017, 3:02pm UTC](https://discuss.elastic.co/t/use-of-index-merge-policy-reclaim-deletes-weight-in-2-3/73746/5 "2017-02-03T15:02:06Z")

</div>

How, thru the REST interface?

I tried that, and saw this in the log: "[2017-02-03 08:39:42,523][WARN][action.admin.cluster.settings] [water] ignoring transient setting [index.merge.policy.reclaim\_deletes\_weight], not dynamically updateable".

---

<div class="post-metadata">

**Author:** ![abeyad](https://avatars.discourse-cdn.com/v4/letter/a/278dde/32.png) [@abeyad](https://discuss.elastic.co/u/abeyad)\
**Post date:** [February 3, 2017, 4:07pm UTC](https://discuss.elastic.co/t/use-of-index-merge-policy-reclaim-deletes-weight-in-2-3/73746/6 "2017-02-03T16:07:47Z")

</div>

I tried it on a 2.4 instance and it worked for me. Using curl:

`curl -XPUT localhost:9200/{index_name}/_settings -d '{ "index.merge.policy.reclaim_deletes_weight": 1.3 }'`

---

<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 3, 2017, 4:08pm UTC](https://discuss.elastic.co/t/use-of-index-merge-policy-reclaim-deletes-weight-in-2-3/73746/7 "2017-03-03T16:08:05Z")

</div>

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