[
https://issues.apache.org/jira/browse/FLINK-10534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649327#comment-16649327
]
ouyangzhe commented on FLINK-10534:
-----------------------------------
[~gjy] , If I want to get job result back or run multi jobs in main method
like shown below, detach mode is not suitable,
{code:java}
xxx = resultDataSet.collect();
// use xxx to do something then sumbit another job
env.execute("test");{code}
now, A session cluster will be started for this case, in CliFrontend.java:
{code:java}
final ClusterSpecification clusterSpecification =
customCommandLine.getClusterSpecification(commandLine);
client = clusterDescriptor.deploySessionCluster(clusterSpecification);
{code}
the session cluster may not be shut down if user's main process killed, and
will always be running in the yarn cluster.
> Add idle timeout for a flink session cluster
> --------------------------------------------
>
> Key: FLINK-10534
> URL: https://issues.apache.org/jira/browse/FLINK-10534
> Project: Flink
> Issue Type: New Feature
> Components: Cluster Management
> Affects Versions: 1.7.0
> Reporter: ouyangzhe
> Assignee: ouyangzhe
> Priority: Major
> Attachments: 屏幕快照 2018-10-12 上午10.24.08.png
>
>
> The flink session cluster on yarn will aways be running while has no jobs
> running at all, it will occupy the yarn resources for no use.
> Taskmanagers will be released after an idle timeout, but jobmanager will keep
> running.
> I propose to add a configuration to limit the idle timeout for jobmanager
> too, if no job running after a specified timeout, the flink cluster auto
> finish itself.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
