# ElasticSearch node shutdown problem

**URL:** <https://discuss.elastic.co/t/elasticsearch-node-shutdown-problem/31247>\
**Category:** Elasticsearch\
**Created:** [September 28, 2015, 9:48am UTC](https://discuss.elastic.co/t/elasticsearch-node-shutdown-problem/31247 "2015-09-28T09:48:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rishabh.poddar](https://avatars.discourse-cdn.com/v4/letter/r/54ee81/32.png) [@rishabh.poddar](https://discuss.elastic.co/u/rishabh.poddar)\
**Post date:** [September 28, 2015, 9:48am UTC](https://discuss.elastic.co/t/elasticsearch-node-shutdown-problem/31247/1 "2015-09-28T09:48:54Z")

</div>

Hi. I am quite new to elastic search. However, after playing with it for sometime, I noticed a problem:  
(I tested the below procedure on Mac OS X as well as Ubuntu 14.04 and they both showed the same problem)

I started an instance of elastic search, call it instance1, on localhost. I then ran the following command: curl -X GET [http://127.0.0.1:9200/\_cluster/health?pretty=true](http://127.0.0.1:9200/_cluster/health?pretty=true). This showed me that one node was alive. All well. I then started another instance, instance2, on the same machine and re-ran the same curl command and got 2 nodes were alive. This is all as expected. I then shut down instance1 (instance2 was still running) and ran the curl command. This should have shown me that 1 node is alive, however it showed curl: (7) Failed to connect to 127.0.0.1 port 9200: Connection refused.

Also, for more information, I did the same procedure all over again and instead of shutting down instance1, I shut down instance2 and then ran the curl command. Here I had no problems and it showed that 1 node was alive. So I think this problem occurs only when the initial instance is shut down.

Is this a bug or am I doing something wrong?

---

<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:** [September 28, 2015, 10:15am UTC](https://discuss.elastic.co/t/elasticsearch-node-shutdown-problem/31247/2 "2015-09-28T10:15:13Z")

</div>

When you start the second node you will notice that it runs on port 9201 and 9301, because the first instance takes 9200/9300.

So if you run `http://127.0.0.1:9201/_cluster/health?pretty=true` after shutting down the first node you will get a response.

---

<div class="post-metadata">

**Author:** ![rishabh.poddar](https://avatars.discourse-cdn.com/v4/letter/r/54ee81/32.png) [@rishabh.poddar](https://discuss.elastic.co/u/rishabh.poddar)\
**Post date:** [September 28, 2015, 10:54am UTC](https://discuss.elastic.co/t/elasticsearch-node-shutdown-problem/31247/3 "2015-09-28T10:54:58Z")

</div>

Thank you.

---

<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:47pm UTC](https://discuss.elastic.co/t/elasticsearch-node-shutdown-problem/31247/4 "2017-07-05T23:47:48Z")

</div>