# In ES 2.3, is there a way to stop \_optimize/\_forcemerge?

**URL:** <https://discuss.elastic.co/t/in-es-2-3-is-there-a-way-to-stop--optimize--forcemerge/73738>\
**Category:** Elasticsearch\
**Created:** [February 2, 2017, 6:48pm UTC](https://discuss.elastic.co/t/in-es-2-3-is-there-a-way-to-stop--optimize--forcemerge/73738 "2017-02-02T18:48:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![trevan](https://avatars.discourse-cdn.com/v4/letter/t/7feea3/32.png) [@trevan](https://discuss.elastic.co/u/trevan)\
**Post date:** [February 2, 2017, 6:48pm UTC](https://discuss.elastic.co/t/in-es-2-3-is-there-a-way-to-stop--optimize--forcemerge/73738/1 "2017-02-02T18:48:33Z")

</div>

I typed in the wrong index name when I started the \_optimize and I would have like to have stopped it instead of having to wait.

Is there a way to cancel them or stop them? I'm using ES 2.3 and I tried doing a \_task/cancel call but it said it could not be canceled. Would closing the index stop it? What about moving the shards?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 2, 2017, 7:23pm UTC](https://discuss.elastic.co/t/in-es-2-3-is-there-a-way-to-stop--optimize--forcemerge/73738/2 "2017-02-02T19:23:30Z")

</div>

Only by restarting the entire cluster.

---

<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 2, 2017, 7:24pm UTC](https://discuss.elastic.co/t/in-es-2-3-is-there-a-way-to-stop--optimize--forcemerge/73738/3 "2017-03-02T19:24:53Z")

</div>

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