You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/07/09 08:02:00 UTC
[jira] [Commented] (FLINK-13162) Default value of slot.idle.timeout
is too large for batch job
[ https://issues.apache.org/jira/browse/FLINK-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881031#comment-16881031 ]
Till Rohrmann commented on FLINK-13162:
---------------------------------------
I don't fully understand the problem [~zjffdu]. Is the problem that a {{JobMaster}} needs to wait for 50s until an idle slot has been released by another {{JobMaster}} if there are multiple jobs running in the same cluster?
> Default value of slot.idle.timeout is too large for batch job
> -------------------------------------------------------------
>
> Key: FLINK-13162
> URL: https://issues.apache.org/jira/browse/FLINK-13162
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Configuration, Runtime / Coordination
> Affects Versions: 1.9.0
> Reporter: Jeff Zhang
> Priority: Major
>
> The default value of slot.idle.timeout is 50 seconds, it is too large for batch job.
> It will cause downstream vertex unable to start even the upstream vertex is finished. It has to wait for 50 seconds. The default value of this kind of configuration doesn't make sense for batch job.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)