| Panel |
|---|
On This Page:
|
Running
When the Slave System Monitors are started (by a service, script or manually) they will optionally wait for the ServiceScheduling database server to become available. They will then sit in an idle state until requested to manage a component on that node on behalf of the Master System Monitor.
...
If a node fails or the Slave System Monitor is not running, then the Master System Monitor will treat all the components on that node as unavailable. The ServiceOptimizer instance will however continue to operate.
Stopping
In order to shut down a distributed ServiceOptimizer instance only the Master System Monitor needs to be stopped (by a service, script or manually). All the components will be stopped except for the Slave System Monitors which can be left running until the instance is restarted.
...