Use of index.merge.policy.reclaim_deletes_weight in 2.3


#1

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.


(Ali Beyad) #2

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


#3

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


(Ali Beyad) #4

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.


#5

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".


(Ali Beyad) #6

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 }'


(system) #7

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