[
https://issues.apache.org/jira/browse/FLINK-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16343323#comment-16343323
]
mingleizhang commented on FLINK-6160:
-------------------------------------
I found all components such as {{TaskExecutor}}, {{JobMaster}} and
{{ResourceManager}} all implements the {{HeartbeatListener}} interface, But
none of them retry to each other while timeout comes. I think all of them
should have a retry action indeed.
> Retry JobManager/ResourceManager connection in case of timeout
> ---------------------------------------------------------------
>
> Key: FLINK-6160
> URL: https://issues.apache.org/jira/browse/FLINK-6160
> Project: Flink
> Issue Type: Sub-task
> Components: Distributed Coordination
> Affects Versions: 1.3.0
> Reporter: Till Rohrmann
> Priority: Major
> Labels: flip-6
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
