Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Invalid
-
1.1.0
-
None
-
None
Description
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.