[
https://issues.apache.org/jira/browse/FLINK-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881640#comment-16881640
]
Jeff Zhang commented on FLINK-13162:
------------------------------------
[~till.rohrmann] This happens in one single job. Here's the screenshot I take.
In this screenshot, the upstream vertex take over all the available slots (2
slot). And after these 2 vertices finish, the third vertex can not start
because the slots are not released by the upstream 2 vertices. Only after 50
seconds, the third vertex can start.
!image-2019-07-10-09-19-34-513.png!
> 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: Improvement
> Components: Runtime / Configuration, Runtime / Coordination
> Affects Versions: 1.9.0
> Reporter: Jeff Zhang
> Priority: Major
> Attachments: image-2019-07-10-09-19-34-513.png
>
>
> 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)
