...
- In case where there is no connection loss:
- the Master sends a HTTP Request to the Agent
- the Agent sends to the Master
- a heartbeat after 10s to the Master should no other HTTP operation on behalf of the Master be executed.
- a HTTP response when an operation is executed on behalf of the Master.
- In case of connection loss after the Master has sent a first HTTP Request:
- the Master waits 12s for the heartbeat from the Agent to arrive
- The Agent should answer with a heartbeat after 10s. This is the Hearbeat Heartbeat Period specified above.
- The Master waits 2s more just in case - this is the Heartbeat Delay specified above.
- If a heartbeat from the Agent came between 10s and 12s (=10s Heartbeat Period + 2s Heartbeat Delay), any running tasks will be continued and completed by the Agent.
- If the Master did not receive the heartbeat from the Agent after 12s, the Master will repeat the first HTTP Request sent 12s ago until the Agent is able to answer
- If the Agent is able to answer before 60s effected - that is, 48s after the HTTP Request repeat, any running tasks will be continued and completed by the Agent. Even though there were more HTTP Requests from the Master, the tasks will be executed just once.
- If the Agent is not able to answer before 60s effected - that is, 48s after the HTTP Request repeat, the Master will kill any running tasks on the Agent.
- the Master waits 12s for the heartbeat from the Agent to arrive
...