[jira] [Comment Edited] (FLINK-6434) There may be allocatedSlots leak in SlotPool

["shuai.xu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000232#comment-16000232 ] 

shuai.xu edited comment on FLINK-6434 at 5/8/17 7:11 AM:
---------------------------------------------------------

[~till.rohrmann] This seems can not fix the bug completely, as between allocateSlot(allcationID1) and failAllocation(allcoationID1), another free slot with allocationID2 may fulfill the pending request, and the allocatedSlots record it will allocationID2, failAllocation(allcoationID1) can not release it, the slot is still leaked.


was (Author: tiemsn):
[~till.rohrmann] This seems can not fix the bug totally, as between allocateSlot(allcationID1) and failAllocation(allcoationID1), another free slot with allocationID2 may fulfill the pending request, and the allocatedSlots record it will allocationID2, failAllocation(allcoationID1) can not release it, the slot is still leaked.

> There may be allocatedSlots leak in SlotPool
> --------------------------------------------
>
>                 Key: FLINK-6434
>                 URL: https://issues.apache.org/jira/browse/FLINK-6434
>             Project: Flink
>          Issue Type: Bug
>          Components: Cluster Management
>            Reporter: shuai.xu
>            Assignee: shuai.xu
>              Labels: flip-6
>
> If the call allocateSlot() from Execution to Slotpool timeout, the job will begin to failover, but the pending request are still in SlotPool, if then a new slot register to SlotPool, it may be fulfill the outdated pending request and be added to allocatedSlots, but it will never be used and will never be recycled.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)