In case of a heartbeat timeout, the TaskExecutor closes the connection to the remote component. Furthermore, it assumes that the component has actually failed and, thus, it will only start trying to connect to the component if it is notified about a new leader address and leader session id. This is brittle, because the heartbeat could also time out without the component having crashed. Thus, we should add an automatic retry to the latest known leader address information in case of a timeout.
- The registration should be retried until a time limit expires after which the TaskExecutor terminates