Page History

...

• We assume a Primary JobScheduler with the start option -exclusive.
• Backup JobSchedulers will use the start options:
  • -exclusive 
  • -backup 
  • -backup-precedence=n
    • where n is a number.
    • The option -backup-precedence is optional and the number n defines the order in which the Backup JobSchedulers become active.
• Exclusively the Primary JobScheduler will be active once all the JobSchedulers have been started.
• All JobSchedulers in the cluster use the same configuration (jobs, job chains, orders, etc.). In particular, the configuration files of the orders must have the same modification date.
• A Backup JobScheduler will not become active if the Primary JobScheduler terminates in a normal way.
• If the Primary JobScheduler is aborted or its process is killed (e.g. the server crashes) then the (next) Backup JobScheduler will become active and will be aware of the job states and order states. That is, the 'new' JobScheduler will be aware of whether 
  • jobs or job chains are stopped or active, 
  • job chain nodes are stopped, skipped or active,
  • orders are suspended or active and 
  • what their current state is.
• The Backup JobScheduler waits 1-2 minutes to be sure that the Primary JobScheduler is dead before it goes active.
  
  • All starts of jobs or orders that would take place within this time will be lost and they runs on the next scheduled time.
• If a Backup JobScheduler is active and the primary JobScheduler is restarted then the Backup JobScheduler has to be terminated in order to reactivate the Primary JobScheduler.

...