Product Knowledge Base

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

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

Feature

Agent Bundles

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): 
      • 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 contacted
      • 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
    • FEATURE AVAILABILITY STARTING FROM RELEASE 1.9

Delimitation

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

Implementation

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

  • No labels