[
https://issues.apache.org/jira/browse/FLINK-9884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann updated FLINK-9884:
---------------------------------
Fix Version/s: 1.5.5
1.6.2
1.7.0
> Slot request may not be removed when it has already be assigned in slot
> manager
> -------------------------------------------------------------------------------
>
> Key: FLINK-9884
> URL: https://issues.apache.org/jira/browse/FLINK-9884
> Project: Flink
> Issue Type: Bug
> Components: Cluster Management
> Affects Versions: 1.5.3, 1.6.0, 1.7.0
> Reporter: shuai.xu
> Assignee: shuai.xu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0, 1.6.2, 1.5.5
>
>
> When task executor report a slotA with allocationId1, it may happen that slot
> manager record slotA is assigned to allocationId2, and the slot request with
> allocationId1 is not assigned. Then slot manager will update itself with
> slotA assigned to allocationId1, by it does not clear the slot request with
> allocationId1.
> For example:
> # There is one free slot in slot manager.
> # Now come two slot request with allocationId1 and allocationId2.
> # The slot is assigned to allocationId1, but the requestSlot call timeout.
> # SlotManager assign the slot to allocationId2 and insert a slot request
> with allocationId1.
> # The second requestSlot call to task executor return SlotOccupiedException.
> # SlotManager update the slot to allocationID1, but the slot request is left.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
