Till Rohrmann closed FLINK-6160.
    Resolution: Fixed

Fixed via 
master: c832f52a9ca489b72e3eddcb51c288d23d66b571
1.5.0: ba379ec0ee451fee807798094f2948741489a263

>  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, 1.5.0, 1.6.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Blocker
>              Labels: flip-6
>             Fix For: 1.5.0
> 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.
> *Acceptance criteria:*
>  - The registration should be retried until a time limit expires after which 
> the {{TaskExecutor}} terminates

This message was sent by Atlassian JIRA

Reply via email to