Page History
...
- the Active Controller Instance is stopped normally from the command line:
controller.sh | .cmd stop
- the Active Controller Instance is restarted normally from the command line:
controller.sh | .cmd restart
- the operating system is shut down and
systemd/init.dor a Windows Service are in place to stop the Controller normally.
...
- the Active Controller Instance is stopped normally from the command line:
controller.sh | .cmd stop
- the Active Controller Instance is restarted normally from the command line:
controller.sh | .cmd restart
- the operating system is shut down and
systemd/init.dor a Windows Service are in place to stop the Controller normally.
...
- The cluster has to guarantee that only one of both Standalone Controller instances is started at any point in time.
- IF If this rule is not 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 instances' journals that are available from the
statesub-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 condition 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 is working.
- Log file analysis is pointless. Controllers heavily make use of asynchronous operations when it comes to Agents. Occurrence of error messages in log files includes allowing a situation to be recovered within the next few seconds.
- A Controller Cluster guarantees high availability when used with a JS7 - Agent Cluster. Use of Standalone Agents limits high availability.
...
Overview
Content Tools