[
https://issues.apache.org/jira/browse/FLINK-15806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann resolved FLINK-15806.
-----------------------------------
Resolution: Fixed
Done via
master:
62ea66f7c0a20de6b8506da6224e1f07da08e5d0
d6fa9c6484b4a54fdf66e58a466f64beca40f8a0
1.10.1:
cc3f2c02173fb96d75902d8479f6cd7375f85a34
9617d58b7f7e6a21941ad3551dc4bdcda11ca074
> 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
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
