You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/09/27 10:06:00 UTC

[jira] [Updated] (FLINK-6152) Yarn session CLI tries to shut cluster down too agressively in interative mode

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

ASF GitHub Bot updated FLINK-6152:
----------------------------------
    Labels: pull-request-available  (was: )

> Yarn session CLI tries to shut cluster down too agressively in interative mode
> ------------------------------------------------------------------------------
>
>                 Key: FLINK-6152
>                 URL: https://issues.apache.org/jira/browse/FLINK-6152
>             Project: Flink
>          Issue Type: Bug
>          Components: Command Line Client
>    Affects Versions: 1.2.0, 1.3.0
>            Reporter: Yelei Feng
>            Assignee: Yelei Feng
>            Priority: Major
>              Labels: pull-request-available
>
> Once yarn session CLI can't get cluster status, it shuts the cluster down and cleanup related files even if new jobmanger will be created soon. As result, AM restarting will fail due to missing files on HDFS
> reproduce step: 
> 1. start yarn session in interactive mode
> 2. kill jobmanager process
> 3. yarn session client can't get cluster status in lookup time and hence trigger shutdown hook which would delete local properties files and files on HDFS, but it can't shutdown the cluster since it can't connect to jobmanager.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)