You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2016/06/17 08:51:05 UTC

[jira] [Closed] (FLINK-3863) Yarn Cluster shutdown may fail if leader changed recently

     [ https://issues.apache.org/jira/browse/FLINK-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maximilian Michels closed FLINK-3863.
-------------------------------------
    Resolution: Fixed

Fixed with 9e9842410a635d183a002d1f25a6f489ce9d6a2f

> Yarn Cluster shutdown may fail if leader changed recently
> ---------------------------------------------------------
>
>                 Key: FLINK-3863
>                 URL: https://issues.apache.org/jira/browse/FLINK-3863
>             Project: Flink
>          Issue Type: Bug
>          Components: YARN Client
>    Affects Versions: 1.1.0, 1.0.2
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: Minor
>             Fix For: 1.1.0
>
>
> The {{ApplicationClient}} sets {{yarnJobManager}} to {{None}} until it has connected to a newly elected JobManager. A shutdown message to the application master is discarded while the ApplicationClient tries to reconnect. The ApplicationClient should retry to shutdown the cluster when it is connected to the new leader. It may also time out (which currently is always the case).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)