We perform rolling upgrades on Elasticsearch cluster in our production environment. Current version of Elasticsearch is 1.3.4 and we're running it on Windows Server 2012 machines. Rolling upgrade needs each node to be stopped one at a time. We use "service.bat stop" to do so. Sometimes this operation successfully stops Elasticsearch service quickly but some other times, it does not stop for a very long time and we resort to killing the process from Task Manager. Obviously this is not the most elegant way to do things but we've been getting away with it till now. In Elasticsearch documents regarding rolling upgrade, it is mentioned to use Nodes Shutdown API <http://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-nodes-shutdown.html> to stop Elasticsearch. Apparently both do the same thing but I'm not sure about it and hence asking in this forum. Below are some of my queries hoping somebody will be able to answer in this group:
1. Do "service.bat stop" and Nodes Shutdown API behave exactly in the same way? 2. When "service.bat stop" is stuck for a very long time (more than 30 minutes), what is the recommended way to do a graceful shutdown or at least know the consequences of killing the process from Task Manager? -- Please update your bookmarks! We moved to https://discuss.elastic.co/ --- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c6f3abcf-c6a7-4a77-b273-bfae73b65013%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
