[
https://issues.apache.org/jira/browse/FLINK-10534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16647972#comment-16647972
]
ouyangzhe commented on FLINK-10534:
-----------------------------------
Thanks [~till.rohrmann] ,
The flink session cluster will be created by two cases:
1. Flink sessions started by user through yarn-session.sh
2. User runs flink programs in interactive mode, firstly a flink session
cluster will be started, the cluster may be shut down if user programs finished
properly, but if user main program crashed or killed. the session cluster maybe
residual.
so I propose to add an idle timeout configuration, let user have the ability to
handle this problem.
> 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)
