solidDB Help : solidDB Grid : Failure handling in the grid : Node controller : Using the node controller
  
Using the node controller
Note Check the solidDB Release Notes for any limitations that are associated with using a grid in the current release.
A node controller requires a working directory that is separate from the working directory of any solidDB grid nodes that run on the same machine. When started and configured, the node controller monitors specified ports for server processes.
When a responsive server is detected, the node controller registers the server working directory and the command line options that should be used to restart the server when required.
Note There is no way to pass information about the server working directory and command line options to the node controller other than by starting the grid node and letting the node controller access the node.
To set up the node controller, complete the following steps:
1 Copy the node controller executable solnc (solnc.exe on Windows) to its own working directory.
2 Configure controller.ini with the solidDB ports on which the controller should listen, see Controller.ini file. For example:
[controller]
Nodes=tcp 1323
3 Start the node controller.
The node controller starts monitoring the configured ports and logs status information to ncmsg.out in the node controller working directory, for example:
2020-02-26 10:43:16: ----------------------------
2020-02-26 10:43:16: solidDB Grid Node Controller
2020-02-26 10:43:16: Version: 200.0.0.1 Build 2020-02-17 MT
2020-02-26 10:43:16: ----------------------------
2020-02-26 10:43:16: N/A 'tcp 1323' Starting to monitor Grid node
2020-02-26 10:45:27: 5956 'tcp 1323' Serving
Messages are also printed to the screen unless the node controller is started with the –q (silent) command line option.
If a solidDB node is terminated or crashes, the node is automatically restarted, and the action is logged in ncmsg.out, for example:
2020-02-26 10:45:48: 5956 'tcp 1323' Dead: Process has disappeared
2020-02-26 10:45:49: 4160 'tcp 1323' Server: Restarted
2020-02-26 10:45:51: 4160 'tcp 1323' Serving
Go up to
Node controller