Page History

Scope

Master

...

Master Cluster

Feature

• JobScheduler Master supports Cluster Operation with redundancy of the involved cluster members.
  • see Passive Cluster
  • see Active Cluster
  • see Master / Agent Cluster
• Clustering is frequently used for high-availability and in some cases for improved performance.

Agent

...

Cluster

Image RemovedImage Added

Feature

• The JobScheduler allows multiple Agents to be specified for a single Process Class.
  • The JobScheduler Master contacts Agents in round-robin mode:Agents 
    • by fixed priority scheduling:
      • JobScheduler Master will select the first available Agent for execution of jobs.
      • If an Agent is not available then the next available Agent is selected from the Agent Cluster.

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

    1188

    • • 1554

    • by round-robin schedulung:
      • JobScheduler Master switches the Agent for each job execution.
      • If an Agent is not available then the next available Agent is selected from the Agent Cluster.

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

    • If the designated
     
    • the first Agent that is configured to execute jobs for the process class will be contacted.
    • if the first Agent is not available then the next Agent listed in the process class configuration will be contactedthis . This procedure will be repeated until an Agent is found that can execute the job.
  • Use cases for this scenario include
    • all Agents running on different server nodes: the switch to the next available Agent implements a fail-over to the next server node.
    • a number of Agents running on the same server node: the switch to the next available Agent implements redundancy  of Agents within a single server node.
• Feature Availability

  • Display feature availability
    StartingFromRelease 1.9

...

• This feature is not intended for load sharing as the JobScheduler will always use the first available Agent.
• This feature is not intended for scalability as it does not allow the execution of jobs in parallel on a number of Agents (clustering).

References

Change Management References

See also

• How to use Agents with Fixed Priority Scheduling and Round-Robin Scheduling