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?