| Table of Contents |
|---|
Scope
- Resilience and Redundancy improve the JobScheduler availability for a number of outage scenarios.
- Master / Agent Redundancy includes a number of architecture decisions:
- Master Clusters provide redundancy of Master instances in a network.
- Agent Bundles can be used to compensate the outage of a server that runs an Agent.
- Master / Agent Resilience includes a number of implicit and explicit measures for:
- Master / Agent Reconciliation allows continued execution of tasks in case of short-term Network Connection Loss.
- Master Service Recovery includes supported measures after a Master Service Failure.
- Database Service Recovery includes the capability to recover in case of Database Connection Loss.
Master / Agent Redundancy
Master Cluster
...
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
Master Cluster
Feature
- JobScheduler Master supports Cluster Operation with redundancy of the involved cluster members.
Agent Bundles
- Clustering is frequently used for high-availability and in some cases for improved performance.
Agent Cluster
Feature
- The JobScheduler allows multiple Agents to be specified for a single Process Class.
- The JobScheduler Master contacts Agents in round-robin mode (JS-1188): 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-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.
- by fixed priority scheduling:
- 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.
- The JobScheduler Master contacts Agents in round-robin mode (JS-1188): Agents
- 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
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
See also