Scope

Resilience is about the availability and robustness of an architecture for a number of outage scenarios.
Master / Agent Availability 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 and possible data loss.

Master / Agent Availability

JobScheduler allows multiple Agents to be specified for a single Process Class.
- JobScheduler 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.
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).
Feature Availability
- FEATURE AVAILABILITY STARTING FROM RELEASE 1.9

JS-1188 - Getting issue details... STATUS

- - jobs that have been enqueued and
  - jobs that are scheduled for execution using start time events.
- All job starts that are delayed due to paused mode will be executed after the JobScheduler Master is continued.
  - This also applies to jobs that are enqueued while paused mode is active.
  - The operation to continue JobScheduler is available with JOC.
- Paused mode allows users to manually check the job history and optionally remove enqueued tasks if Agent Reconciliation has not taken place.
  - The Agent stores log files of jobs during execution. If an execution result cannot be reported to the Master then the log file will be retained, otherwise it will be removed (JS-1521).
  - Paused mode can be configured to be applied automatically in case of restart of a JobScheduler Master after failure (JS-1522).
Delimitation
- The currently supported measures include manual checking after failure.
- Automated recovery of the Master/Agent execution status after a Master Service Failure is subject to future improvements.
Feature Availability
- FEATURE AVAILABILITY STARTING FROM RELEASE 1.10.2

Key	Summary	T	Created	Updated	Due	Assignee	Reporter	P	Status	Resolution

Loading...

Refresh