[
https://issues.apache.org/jira/browse/FLINK-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022400#comment-16022400
]
ASF GitHub Bot commented on FLINK-6152:
---------------------------------------
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/3654
@barcahead thanks for the PR. One side question: how would this change
affect the case where there is no restart, but simply a failure on the JM?
> 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: Client
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Yelei Feng
> Assignee: Yelei Feng
>
> 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
(v6.3.15#6346)
