You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/02/26 16:49:00 UTC

[jira] [Updated] (FLINK-4487) Need tools for managing the yarn-session better

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

Till Rohrmann updated FLINK-4487:
---------------------------------
    Issue Type: New Feature  (was: Improvement)

> Need tools for managing the yarn-session better
> -----------------------------------------------
>
>                 Key: FLINK-4487
>                 URL: https://issues.apache.org/jira/browse/FLINK-4487
>             Project: Flink
>          Issue Type: New Feature
>          Components: YARN
>    Affects Versions: 1.1.0
>            Reporter: Niels Basjes
>            Priority: Major
>
> 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
(v7.6.3#76005)