Page History

...

Agents can be clustered for high-availability and scalability. The motivation for clustering includes:

• High-availability: Should a server node in the scheduling environment fail then jobs are executed with the Agents on remaining server nodes.
• Scalability: A single Agent can execute thousands of jobs in parallel tasks, however, for a number of use cases it is preferable to distribute server load. This applies particularly to applications that require horizontal scaling across a number of server nodes instead of vertical scaling on a more powerful single server node.

...

• Use of Standalone Agents:
  • available to Open Source License holders and to commercial license holders.
  • for details see JS7 - Management of Standalone Agents.
• Use of Agent Clusters:
  • available to commercial license holders,
  • Cluster Agents receive license information from a Controller and do not require license keys to be assigned individually assigned, see JS7 - How to apply a JS7 License Key.

...

Anchor
enable_disable_subagent enable_disable_subagent

Enable/Disable Subagent Subagent

Subagents can be disabled and enabled. They are enabled by default.

• When a Subagent is disabled then it is no longer considered for job execution.
  • At the point in time of disabling the Subagent will continue to complete any tasks running for jobs.
  • No new tasks are added to a disabled Subagent.
  • The remaining Subagent(s) in the cluster will take on over the load.
• When a disabled Subagent is enabled then it is automatically considered for next job executions.
• The assignment of Subagent Clusters that include a disabled Subagent to jobs in a workflow remains unchanged.
  • For clusters that include more than one Subagent the remaining Subagents will execute the jobs.
  • For Subagent Clusters that hold a single disabled Subagent any orders will wait for the Subagent to become available and enabled. When the Subagent is up and running, for example after a restart, and is enabled then orders will automatically continue in the workflow.
• Should a Subagent be disabled that acts as a Director Agent then this will make the Agent Cluster unavailable independently from the fact if Subagents in the Cluster are enabled or up and running.
  • The Director Agent orchestrates Subagents and is required for a functional Cluster.
  • The Dashboard view displays Agent Clusters with a disabled Director Agent being failed.

Disabling of Subagents can be used for example to manage maintenance windows on server nodes.

Anchor
reset_subagent reset_subagent

Reset Subagent

Subagents can be reset in case of problems during initial operation or to re-assign Subagents to a different Subagent Cluster.

• Reset: Any running tasks in a Subagent can continue. The Subagent does not accept new tasks. With running tasks being completed the Subagent will restart.
• Reset Forced: Any running task in a Subagent are killed. The Subagent does not accept new tasks. The Subagent restarts.
• If the Subagent acts as a Director Agent then the following applies:
  • Dropping the Director Agent's journal means that it looses its memory. This operation can be used to seize an Agent, i.e. to assign it a different Controller.
  • This operation should be used with care, for example if an Agent that is assigned a Controller in a production environment is taken over by a Controller of some different environment.
  • After restart of a reset Director Agent the Controller will deploy scheduling objects such as workflows and will submit orders as assigned the Agent.
• If the Subagent is not acting as a Director Agent then after restart it will be assigned tasks by the Director Agent.

Anchor
delete_subagent delete_subagent

Delete Subagent

...

The operation to deploy a Subagent Cluster is available from the Deploy button in the right upper corner:

Anchor
revoke_subagent_cluster revoke_subagent_cluster

Revoke Subagent Cluster

Subagent Clusters can be revoked, i.e. they can be withdrawn from a Controller. As a result the Subagent Cluster's deployment will be undone.

• This operation is possible if no jobs are assigned the Subagent Cluster. Otherwise users first have to reassign their jobs different Subagent Clusters.
  • Users can apply the Search & Replace function for Subagent Cluster assignments in a workflow that is available from the JS7 - Workflow Editor.
  • Users can apply the JS7 - Inventory Search function to replace Subagent Cluster assignments across workflows.
  • Modified workflows have to be deployed to a Controller to make changes effective.
• With the Subagent Cluster being revoked the Controller does not know the Subagent Cluster any longer. However, the Subagent Cluster configuration in the JOC Cockpit inventory remains in place and can be deployed later on.

Anchor
delete_subagent_cluster delete_subagent_cluster

Delete Subagent Cluster

...