| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
General
Multiple JobScheduler can built Two or more JobSchedulers can be operated as a cluster.
All JobScheduler of the JobSchedulers in a cluster must have the same Id and must use the same database.
Furthermore Further, each JobScheduler of in a cluster must start be started with one of the following cluster options:
- -exclusive
- -exclusive -backup
- -distributed-orders
Look at See http://www.sos-berlin.com/doc/en/scheduler.doc/command_line.xml for more information about JobScheduler start options.
JobScheduler Cluster
Three different types of JobScheduler cluster can be configured, depending on the cluster start options used:
JobScheduler Clusters
All JobSchedulers All JobScheduler of this cluster type have the start option -exclusive.After you have start all JobScheduler of this cluster only the first one is active
Only the primary JobScheduler will be active once all the JobSchedulers in this type of cluster have been started.
The other JobScheduler are JobSchedulers will be waiting for activation.
We assume that all JobScheduler JobSchedulers in this type of the cluster will have the same configuration (Jobs, Job Chains, Orders, etc.)
If you terminate the active JobScheduler is terminated for whatever reason then one of the other others will go automatically become active automatically and knows all states, i.e. wether the be aware of all the job and order states. That is, the 'new' JobScheduler will be aware of whether Jobs or Job Chains are stopped or notactive, whether Job Chain Nodes are stopped, skipped or not, active and whether Orders are suspended or not active and on which step they were at.
JobScheduler Backup
...
Clusters
Here we have a primary JobScheduler which has with the start option -exclusive.
All other Backup JobScheduler will have the start option -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 another JobScheduler goes active when necessary.the backup JobSchedulers become active.
Only After you have start all JobScheduler of this cluster only the primary JobScheduler is activewill be active once all the JobSchedulers in this type of cluster have been started.
We assume that all JobScheduler of the cluster have the same configuration (Jobs, Job Chains, Orders, etc.)
A Backup JobScheduler in this type of this cluster doesnwon't start when you have terminate the primary JobScheduler terminates in a normal way.
But when you abort the primary JobScheduler is aborted or its process is killed (e.g. the Server has crashedcrashes) then the (next) Backup JobScheduler goes will become active and knows all states, i.e. wether the be aware of all the job and order states. That is, the 'new' JobScheduler will be aware of whether Jobs or Job Chains are stopped or notactive, whether Job Chain Nodes are stopped, skipped or not, active and whether Orders are suspended or not active and on which step they were at.
If a Backup JobScheduler is active and the primary JobScheduler is restarted then you must terminate the Backup JobScheduler has to be terminated in order to reactivate the primary.
See also http://www.sos-berlin.com/doc/en/scheduler.doc/backupscheduler.xml
JobScheduler Load Balancing
...
Clusters (Distributed Orders)
All JobScheduler JobSchedulers in this type of this cluster have the start option -distributed-orders.After you have start all JobScheduler of this cluster then all are active
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 Jobs alone except Orders of own Jobs independantly, with the exception of Orders for Job Chains which are configured as distributed.
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?
During the installer you can choose You can set cluster options .
For later configuration you must edit the file during installation of the JobScheduler.
After installation has been completed, cluster options can be set by editing the ./user_bin/jobscheduler_environment_variables file.(sh|cmd).
Example: ./user_bin/jobscheduler_environment_variables.sh on Unix
...
See also http://www.sos-berlin.com/doc/en/scheduler_installation.pdf
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 is displayed.
Here you see a list of all will be displayed, showing all the cluster members.
Example: Backup Cluster
