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 2020/01/29 16:56:00 UTC
[jira] [Updated] (FLINK-15806) Update recommended way to shut down
detached Yarn session cluster
[ https://issues.apache.org/jira/browse/FLINK-15806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-15806:
-----------------------------------
Labels: pull-request-available usability (was: usability)
> Update recommended way to shut down detached Yarn session cluster
> -----------------------------------------------------------------
>
> Key: FLINK-15806
> URL: https://issues.apache.org/jira/browse/FLINK-15806
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Affects Versions: 1.10.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: pull-request-available, usability
> Fix For: 1.11.0, 1.10.1
>
>
> When starting a Yarn session cluster in detached mode, then it is printed that one should shut down the cluster via {{yarn application -kill}}. The problem of this approach is, however, that temporary files won't be cleaned up which remain on HDFS. Hence, I think a better way would be to reconnect via the {{yarn-session.sh}} tool and then to stop the cluster gracefully. This won't leave orphaned files behind.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)