[
https://issues.apache.org/jira/browse/FLINK-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881800#comment-16881800
]
Yang Wang commented on FLINK-13162:
-----------------------------------
Hi [~zjffdu]
This may happen in blink, but not in flink now.
In blink, the free slots cached in slot pool could not be used by downstream
vertices because of the resource profiles are different.
However, in flink, the free slots could be used by downstream vertices. The
resource profiles are all `UNKNOWN`.
> 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)
