[
https://issues.apache.org/jira/browse/FLINK-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881897#comment-16881897
]
Till Rohrmann commented on FLINK-13162:
---------------------------------------
Thanks for the clarification [~zjffdu], [~fly_in_gis] and [~xintongsong]. Now I
understand the problem. I think for 1.9 we don't have time to fix this problem
because the feature freeze is tomorrow. However, for the next release, we
should think a bit how the whole resource management and slot allocation should
work holistically. I hope that we can find a good model in which these problems
will be resolved.
> 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)
