Stopping a node
You can stop a node immediately, which is not recommended, or in a controlled fashion, which gives the node 60 seconds to clean up.
Normally, you do not stop individual application nodes. Instead, you stop an entire application and, as a result, all nodes belonging to the application will be stopped. However, there are situations when you want to stop an individual application node.
For example:
- A node is experiencing problems and you need to stop it, perhaps with the intention of starting a new node to replace the stopped one.
- The application has been started in multiple instances (nodes) but all that capacity is no longer required, so some of the nodes can be removed to free resources.
- You want to clear a particular host in a multi-host grid from all nodes to perform some maintenance on that host.
Before stopping a node, note these considerations:
- Should the node be put in an offline state first?
- If the application node is the only one of its kind, the application may stop working. Should a new similar application node be started first before the node is stopped?
- Applications are implemented differently. Some applications manage their nodes themselves.
- Consult the documentation of the application. Does the documentation recommend an alternative procedure to stopping the node in this case?