...

• The Agent Cluster brings horizontal scalability and fail-over capabilities for Agents.
  • A number of Subagents operated for different servers share the job execution load in an Agent Cluster (active-active clustering).
  • Automated fail-over guarantees high-availability and restart capabilities of an Agent Cluster (active-passive cluster).
• Use of the Agent Cluster is subject to the agreements of the JS7 - License.
• For instructions about how to set up Agent Clusters see the JS7 - Management of Agent Clusters article.
• Development Status:
  • Subagent Cluster:, see 

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

    
    

    Display feature availability
    StartingFromRelease 2.3.0

  • Director Cluster see 

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

    
    

    Display feature availability
    StartingFromRelease 2.56.0

Operational Layer

The architecture applies to the clustering of Director Agents and the clustering of Subagents for high-availability and scalability purposes.

...

• The Subagent inside the Director can be used to execute jobs (not recommended).
• The Director's Subagent can be disabled in order to have the Director only perform orchestration and not execute jobs with its Subagent (recommended).

...

The Director Agent can be operated as a single instance and as a member in a passive Director Cluster of two Director AgentsAgent instances.

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

• Display feature availability
  StartingFromRelease 2.56.0

In a Director Cluster one Director Agent instance holds the active role and the second Director Agent instance holds the passive role.

If the Director Agent is operated as a cluster then the active Director Agent instance synchronizes its journal with the standby Director Agentinstance. If the journals of both active and standby Director Agents Agent instances are in sync then a in case of fail-over (automatically) or switch-over (caused by user intervention) can occur and the Director Agents Agent will switch the active and standby rolesroles.

During fail-over and switch-over of Director Agent instances any jobs running on related Subagents are continued.

Subagent

Subagents come in two shapes: they can be operated as Standalone individual instances and they ship inside a Director Agent.

...

• Subagents execute jobs on behalf of the active Director Agent.
• They report back log output and the execution results of jobs to the active Director Agent.
• If a Subagent fails then the active Director Agent will hand-over the job execution request to the next Subagent.
• A Subagent kills running jobs if the connection from the active Director Agent is lost or if it is instructed by the active Director Agent to suspend/kill or to cancel/kill an order.
  • This behavior is intended to prevent double job execution by more than one Subagent.
  • If the connection from the active Director Agent can be re-established within a given timeout then the Subagent will continue to execute jobs.

...

• A Subagent Cluster is specified by a Selection and Scheduling Mode:
  • The Subagent cluster can include a single Subagent, a number of Subagents or all Subagents.
  • The Scheduling Mode is one of fixed-priority or round-robin.
• Any number of Subagent Clusters can be configured.

...