You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gary Yao (JIRA)" <ji...@apache.org> on 2018/10/13 06:36:00 UTC
[jira] [Comment Edited] (FLINK-10534) Add idle timeout for a flink
session cluster
[ https://issues.apache.org/jira/browse/FLINK-10534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648774#comment-16648774 ]
Gary Yao edited comment on FLINK-10534 at 10/13/18 6:35 AM:
------------------------------------------------------------
[~yeshan] Can you describe why a [per-job cluster|https://ci.apache.org/projects/flink/flink-docs-master/ops/deployment/yarn_setup.html#run-a-single-flink-job-on-yarn] is not an option for you?
was (Author: gjy):
[~yeshan] Can you describe why a per-job cluster is not an option for you?
> 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)