Introduction

• Two or more JobSchedulers can be operated as a cluster.
• All JobSchedulers in a cluster 
  • have to be identified by the same JobScheduler ID and 
  • have to use the same database.
• Furthermore, each JobScheduler in a cluster has to be started with one of the following cluster options:
  • -exclusive
  • -exclusive -backup
  • -distributed-orders
• See http://www.sos-berlin.com/doc/en/scheduler.doc/command_line.xml for more information about JobScheduler start options.
• The following types of JobScheduler clusters can be configured, depending on the cluster start options used.

JobScheduler Cluster

JobScheduler Passive Cluster

• 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.
• 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 http://www.sos-berlin.com/doc/en/scheduler.doc/backupscheduler.xml

JobScheduler Active Cluster

• All JobSchedulers in this type of cluster use the start options -exclusive -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 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

How can I set the cluster start option?

• You can set cluster options during installation of the JobScheduler.
• After the installation has been completed, the cluster options can be set by editing the ./bin/jobscheduler_environment_variables file.(sh|cmd).

Unix

• stop the JobScheduler

   

• edit ./bin/jobscheduler_environment_variables.sh

   SCHEDULER_CLUSTER_OPTIONS=-exclusive
  

• start the JobScheduler

Windows

• stop the JobScheduler service

• remove the JobScheduler service

   .\bin\jobscheduler.cmd remove
  

• modify .\bin\jobscheduler_environment_variables.cmd

   SET SCHEDULER_CLUSTER_OPTIONS=-exclusive
  

• install the JobScheduler service

   .\bin\jobscheduler.cmd install
  

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

Example: Backup Cluster: