Page History

...

• If the Master successfully re-connects to the Agent within the grace period then
  
  • running tasks will be continued and completed by the Agent.
  • the task status and execution result will be reported to the Master.

• In case of reconciliation the task status, log information and execution result are available for the Master and are visible with JOC.

Tasks won't be killed even during longer network outages

• This needs a special configuration at the Process Class which is assign to the Job.
  • The Agent should get a very long Heartbeat Timeout (longer than the outage)
  • Heartbeat Period should also have a higher value in this case, since every failed connection attempt is logged by the master and thus the protocol becomes unnecessarily large, but it is not absolutely necessary.

Configuration

• The heartbeat settings can be configured with the Process Classes that specify the Agent connection. 
• The configuration is located with the Master, no configuration items are stored with the Agent.

...

• Heartbeat Period: http_heartbeat_period
  • The period after which the Agent sends a heartbeat to Master should no other HTTP operation on behalf of the Master be executed.
  • Default: 10s
• Heartbeat Timeout: http_heartbeat_timeout
  • The overall timeout that determines if a connection is considered to be lost permanently.
  • Includes the heartbeat period and the delay after which the Master will send its heartbeat.
  • The Heartbeat Timeout has to be a multiple of the Heartbeat Period
  • Default: 60s

Example

<?xml version="1.0" encoding="utf-8"?>
<process_class>
    <remote_schedulers>
        <remote_scheduler remote_scheduler="http://127.0.0.2:4445" http_heartbeat_period="10" http_heartbeat_timeout="60"/>
    </remote_schedulers>
</process_class>

...

Documentation

• Resilience
• Connection Keep-Alive for Master and Agent

...