Page History
...
- The cluster has to guarantee that only one of both Controller instances is started at any point in time.
- Should this rule not be observed then both Controller instances will instruct Agents to execute the same workflows and jobs which will result in double job execution.
- Controller journals will be messed up with the same orders in different state transitions.
- In this situation the only solution is to drop both Controller instance's journals that are available from the
state
sub-directory, to accept that any orders are lost and to redeploy scheduling objects.
- There is no simple way to determine if a Controller instance is not in perfect shape to manage orders.
- Performing PID file checks is of limited use: this can prove the unavailability of a Controller instance. However, a positive PID file check does not prove that a Controller instance works.
- Log file analysis is pointless. Controllers are heavily making use of asynchronous operations when it comes to Agents. Occurrence of error messages in log files does not prevent a situation to be recovered within the next few seconds.
Further Resources
- JS7 - Initial Operation for Controller Cluster
- JS7 - Management of Controller Clusters
- JS7 - Controller - Command Line Operation
Overview
Content Tools