# Suggested way to shutdownElastic Search cluster in 2.1from client application

**URL:** <https://discuss.elastic.co/t/suggested-way-to-shutdownelastic-search-cluster-in-2-1from-client-application/41280>\
**Category:** Elasticsearch\
**Created:** [February 9, 2016, 2:00pm UTC](https://discuss.elastic.co/t/suggested-way-to-shutdownelastic-search-cluster-in-2-1from-client-application/41280 "2016-02-09T14:00:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![anjith.p](https://avatars.discourse-cdn.com/v4/letter/a/a3d4f5/32.png) [@anjith.p](https://discuss.elastic.co/u/anjith.p)\
**Post date:** [February 9, 2016, 2:00pm UTC](https://discuss.elastic.co/t/suggested-way-to-shutdownelastic-search-cluster-in-2-1from-client-application/41280/1 "2016-02-09T14:00:57Z")

</div>

We have a need to shutdown the ElasticSearch cluster from my client application - installed on different machine . We achieved this functionality using shutdown API in 1.6 which is no longer available from2.0. I'm wondering if there is any suggested way to achieve the same in 2.0:we are considering using the JMX or ES plugin. Please suggest.

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [February 9, 2016, 5:33pm UTC](https://discuss.elastic.co/t/suggested-way-to-shutdownelastic-search-cluster-in-2-1from-client-application/41280/2 "2016-02-09T17:33:55Z")

</div>

> [@anjith.p](#):
>
> Please suggest.

My suggestion is to use the standard process mechanics for your deploy. For most people that means a human taking action with systemd or the init script.

If your application runs elasticsearch all on its own then it should keep a reference to the process it forked and it should kill it.

---

<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 9, 2016, 11:51pm UTC](https://discuss.elastic.co/t/suggested-way-to-shutdownelastic-search-cluster-in-2-1from-client-application/41280/3 "2016-02-09T23:51:00Z")

</div>

> [@anjith.p](#):
>
> We have a need to shutdown the Elasticsearch cluster from my client application

Why is that?

---

<div class="post-metadata">

**Author:** ![anjith.p](https://avatars.discourse-cdn.com/v4/letter/a/a3d4f5/32.png) [@anjith.p](https://discuss.elastic.co/u/anjith.p)\
**Post date:** [February 10, 2016, 4:15am UTC](https://discuss.elastic.co/t/suggested-way-to-shutdownelastic-search-cluster-in-2-1from-client-application/41280/4 "2016-02-10T04:15:22Z")

</div>

The primary reason is BWC - we used to support before. Another reason is that we have many ES nodes running on different machines and we want a centralized mechanism to shutdown them.

---

<div class="post-metadata">

**Author:** ![anjith.p](https://avatars.discourse-cdn.com/v4/letter/a/a3d4f5/32.png) [@anjith.p](https://discuss.elastic.co/u/anjith.p)\
**Post date:** [February 10, 2016, 4:17am UTC](https://discuss.elastic.co/t/suggested-way-to-shutdownelastic-search-cluster-in-2-1from-client-application/41280/5 "2016-02-10T04:17:27Z")

</div>

No Elastic Search runs independently on different machines. Basically we are looking for a centralized mechanism to shutdown all the nodes - preferably from our application.

---

<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 5, 2017, 11:17pm UTC](https://discuss.elastic.co/t/suggested-way-to-shutdownelastic-search-cluster-in-2-1from-client-application/41280/6 "2017-07-05T23:17:43Z")

</div>