Shutting down all nodes shuts down clients nodes and kills host process

Elastic Stack Elasticsearch
1

Hi - Shutting down all nodes (using curl -XPOST
'http://localhost:9200/_shutdown') stops data nodes, but also stops client
nodes, and causes their host process (eg Tomcat if running a client node
inside Tomcat) to exit. Setting "action.disable_shutdown" to true fixes
this issue, but it should probably default to true for client nodes and/or
for nodes running inside another process?

2

Yea, there is a bug there that does not take the correct list of nodes to
shutdown in case of "all" shutdown, opened an issue:
https://github.com/elasticsearch/elasticsearch/issues/1939.

On Thu, May 10, 2012 at 2:59 PM, Michael Snell michael@snell.com wrote:

Hi - Shutting down all nodes (using curl -XPOST '
http://localhost:9200/_shutdown') stops data nodes, but also stops client
nodes, and causes their host process (eg Tomcat if running a client node
inside Tomcat) to exit. Setting "action.disable_shutdown" to true fixes
this issue, but it should probably default to true for client nodes and/or
for nodes running inside another process?

3