# Possible to restrict force merges to single ElasticSearch nodes?

**URL:** <https://discuss.elastic.co/t/possible-to-restrict-force-merges-to-single-elasticsearch-nodes/195790>\
**Category:** Elasticsearch\
**Created:** [August 19, 2019, 5:56pm UTC](https://discuss.elastic.co/t/possible-to-restrict-force-merges-to-single-elasticsearch-nodes/195790 "2019-08-19T17:56:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![prungta](https://avatars.discourse-cdn.com/v4/letter/p/85f322/32.png) [@prungta](https://discuss.elastic.co/u/prungta)\
**Post date:** [August 19, 2019, 5:56pm UTC](https://discuss.elastic.co/t/possible-to-restrict-force-merges-to-single-elasticsearch-nodes/195790/1 "2019-08-19T17:56:14Z")

</div>

The API for `forcemerge` operates per index. I’d like to restrict further to only the segments on a single node.

Few different reasons why I'm after this:  
(1) As things stand, forcemerge(s) cannot be cancelled. Isolating to a single node allows for more control in case of failure/retry.  
(2) Prioritising based on load/resource usage. E.g. in cases of asymmetric distribution of disk usage across the cluster, you'd want to kick off forcemerge in order of disk usage %.

x-post on SO: [https://stackoverflow.com/q/57530609/1095091](https://stackoverflow.com/q/57530609/1095091)

---

<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:** [September 16, 2019, 5:56pm UTC](https://discuss.elastic.co/t/possible-to-restrict-force-merges-to-single-elasticsearch-nodes/195790/2 "2019-09-16T17:56:32Z")

</div>

Closed on September 16, 2019, 5:56pm UTC

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