[
https://issues.apache.org/jira/browse/FLINK-10534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649880#comment-16649880
]
Till Rohrmann commented on FLINK-10534:
---------------------------------------
You're right [~yeshan] that we start a session cluster in the attached per-job
mode which is a legacy artifact. In the future we should rework this and let
every job part start its own per-job cluster.
In the mean time an idleness timeout would solve the problem, I agree. Alright,
let's add it but it should only be used by the "per-job" mode where we launch a
session 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)
