# \[Windows server 2012 R2\] Restarting Elasticsearch sometimes causes it to create and use a new node

**URL:** <https://discuss.elastic.co/t/windows-server-2012-r2-restarting-elasticsearch-sometimes-causes-it-to-create-and-use-a-new-node/36665>\
**Category:** Elasticsearch\
**Created:** [December 8, 2015, 6:25pm UTC](https://discuss.elastic.co/t/windows-server-2012-r2-restarting-elasticsearch-sometimes-causes-it-to-create-and-use-a-new-node/36665 "2015-12-08T18:25:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shadoninja](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@Shadoninja](https://discuss.elastic.co/u/Shadoninja)\
**Post date:** [December 8, 2015, 6:25pm UTC](https://discuss.elastic.co/t/windows-server-2012-r2-restarting-elasticsearch-sometimes-causes-it-to-create-and-use-a-new-node/36665/1 "2015-12-08T18:25:15Z")

</div>

When right clicking on Elasticsearch in the services menu on Windows and click "Restart," sometimes a second node pops up and is used by Elasticsearch for lifetime of that process.

My hypothesis so far:

Windows thinks Elasticsearch is fully stopped before it actually is. Then it starts a new instance too soon and notices that the old node is still locked. It then decides it must be a new node in the cluster and creates and uses a new directory for data storage.

Is this possible? Is there a way i can have delays in Windows service restarting?

---

<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:32pm UTC](https://discuss.elastic.co/t/windows-server-2012-r2-restarting-elasticsearch-sometimes-causes-it-to-create-and-use-a-new-node/36665/2 "2017-07-05T23:32:33Z")

</div>

Closed on July 5, 2017, 11:32pm UTC