[
https://issues.apache.org/jira/browse/FLINK-13165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883556#comment-16883556
]
Till Rohrmann commented on FLINK-13165:
---------------------------------------
Yes agreed. One needs to set the input dependency constraint to ALL. This issue
should simply make the behaviour of the {{SlotPoolImpl}} more predictable in
terms of semantics.
> Complete requested slots in request order
> -----------------------------------------
>
> Key: FLINK-13165
> URL: https://issues.apache.org/jira/browse/FLINK-13165
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.9.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When executing batch jobs with fewer slots than requested we should make sure
> that the slot requests are being completed in the order in which they were
> enqueued into the {{SlotPool}}. Otherwise we might risk that a consumer task
> gets deployed before a producer causing a resource deadlock situation.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)