# Improvements to shutdown API

**URL:** <https://discuss.elastic.co/t/improvements-to-shutdown-api/3097>\
**Category:** Elasticsearch\
**Created:** [July 14, 2010, 1:29pm UTC](https://discuss.elastic.co/t/improvements-to-shutdown-api/3097 "2010-07-14T13:29:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [July 14, 2010, 1:29pm UTC](https://discuss.elastic.co/t/improvements-to-shutdown-api/3097/1 "2010-07-14T13:29:08Z")

</div>

Hi,

In 0.9, I added an improvement to the shutdown API to better perform a  
full cluster shutdown. This is the recommended way to shutdown the full  
cluster (and not killing / stopping processes one by one). When killing /  
stopping nodes one by one, the cluster will start to allocate the shards to  
the remaining nodes, which is wasteful, the cluster wide shutdown API is  
smart enough not to do it.

-shay.banon

---

<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 6, 2017, 4:22am UTC](https://discuss.elastic.co/t/improvements-to-shutdown-api/3097/2 "2017-07-06T04:22:19Z")

</div>