Starting a new node
Starting a new node can be triggered from both the node card and the node list. Click to launch a new node. First select the binding (application name is in italics) and then select the host to launch the node on and finally click .
Application instances are started by launching a binding that targets the correct node type. Normally you do not start individual application nodes. Instead, you start an entire application and, as a result, all nodes belonging to the application will be started.
However, there are situations when you want to start an individual application node. Examples are:
- An application is experiencing increased load and you want to start a new server application instance, perhaps on a new host with spare capacity, to cope with the new situation.
- You intend to stop an existing node and you want to start a new alternative node first so that the operations of the application will not be disturbed when you stop the node.
- You want to move the execution of this application from one host to another. This would be done by starting new nodes on the new host combined with stopping the old nodes on the original host.
Before starting a node, note these considerations:
- Does the application support manually starting new nodes? Some applications manage their own nodes and they should not be started manually.
- Some applications do not support several instances running simultaneously. If that is the case with the application you are starting, existing nodes may have to be stopped first. However, ideally, applications should be written to support this.
- Always consult the application's documentation on what is supported in each case.