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.)
• 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.

See also

...

• How will the watchdog mechanism monitor for cluster fail-over?

• http://www.sos-berlin.com/doc/en/scheduler.doc/backupscheduler.xml

Change Management References

JobScheduler Active Clusters

• All JobSchedulers in this type of cluster use the start options -distributed-orders.
• All the JobSchedulers in this type of cluster will be active once they all have been started.
• Each JobScheduler of this cluster will handle its own jobs independently, with the exception of orders for job chains that are configured as distributed.
• Distributed orders are handled in way that each cluster member can process any step of an order within a job chain. Cluster members use some load balancing logic to determine which JobScheduler instance should process the next job for an order in a job chain.

See also

...

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1177

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-48

• How to configure balanced distributed orders

• How to manage Distributed Orders in JobScheduler clusters

• http://www.sos-berlin.com/doc/en/scheduler.doc/distributed_orders.xml and 
• http://www.sos-berlin.com/doc/en/scheduler.doc/xml/job_chain.xml#attribute_distributed

Change Management References

How can I set the cluster start option?

...

• start the JobScheduler service
• See also JobScheduler Installation Manual

The

...

Cluster tab in JOC

If you open the JobScheduler Operating Center (JOC) of a JobScheduler which is member of a cluster then a Cluster tab will be displayed, showing the cluster members.

...