[ 
https://issues.apache.org/jira/browse/FLINK-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438690#comment-15438690
 ] 

Stephan Ewen commented on FLINK-4487:
-------------------------------------

I think that the last changes for cluster management by [~mxm] will probably 
address most of that.

> Need tools for managing the yarn-session better
> -----------------------------------------------
>
>                 Key: FLINK-4487
>                 URL: https://issues.apache.org/jira/browse/FLINK-4487
>             Project: Flink
>          Issue Type: Improvement
>          Components: YARN Client
>    Affects Versions: 1.1.0
>            Reporter: Niels Basjes
>
> There is a script yarn-session.sh which starts an empty JobManager on a Yarn 
> cluster. 
> Desired improvements:
> # If there is already a yarn-session running then yarn-session does not start 
> a new one (or it kills the old one?). Note that the file with ip/port may 
> exist yet the corresponding JobManager may have been killed in an other way.
> # A script that effectively lets me stop a yarn session and cleanup the file 
> that contains the ip/port of this yarn session and the .flink directory on 
> HDFS.



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

Reply via email to