Distributed Scheduling Recoverability

Communication

When the adTempus Master service starts, it attempts to connect to all defined agents (except those that have been disabled).

If no connection can be made, or if a connection is made and subsequently lost, adTempus will retry the connection approximately every 30 seconds until the connection is re-established.

Queued Commands

If the connection between the Master and an Agent fails, both the Master and the Agent will queue any data and commands that need to be transmitted, and will exchange this data when the connection is re-established.

In some cases, you may want adTempus to just "skip" an agent if it is not connected when a job needs to be run. This can be controlled when you link the agent to the queue.

Independent Operation

If an Agent loses the connection to its Master, this has no effect on any jobs that are already executing, as the Agent has a complete copy of the job's data stored locally.

If the job uses the Slave or Load Balancing agent modes, no new instances of the job will be run until the connection is re-established, as the jobs are triggered only by the Master.

If the job uses Mirrored mode, the Agent will continue to execute the job according to its defined schedule (or other trigger) regardless of whether the Agent is connected to the Master.