[
https://issues.apache.org/jira/browse/FLINK-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-21874:
-----------------------------------
Labels: pull-request-available (was: )
> Check for out-dated slot allocation confirmations is insufficient
> -----------------------------------------------------------------
>
> Key: FLINK-21874
> URL: https://issues.apache.org/jira/browse/FLINK-21874
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.13.0
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.13.0
>
>
> The {{DeclarativeSlotManager}} accounts for the possibility of slot
> allocation confirmations coming in after the slot has already been freed
> fully allocated (e.g., through a SlotReport) by checking whether there is
> still a pending request for that slot.
> However, this only works properly if the slot was allocated.
> If the slot was freed in the mean time then it could've already been
> re-assigned to another job, which result in an IllegalStateException once the
> confirmation arrives.
> It can also happen that the slot is reassigned to the same job, which can
> result in a premature configuratiom of the allocation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
