[
https://issues.apache.org/jira/browse/FLINK-9884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599496#comment-16599496
]
ASF GitHub Bot commented on FLINK-9884:
---------------------------------------
TisonKun edited a comment on issue #6360: [FLINK-9884] [runtime] fix slot
request may not be removed when it has already be assigned in slot manager
URL: https://github.com/apache/flink/pull/6360#issuecomment-417825840
cc @tillrohrmann @GJL
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
> Reporter: shuai.xu
> Assignee: shuai.xu
> Priority: Major
> Labels: pull-request-available
>
> 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)
