You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2017/05/04 14:56:04 UTC
[jira] [Issue Comment Deleted] (FLINK-6434) There may be
allocatedSlots leak in SlotPool
[ https://issues.apache.org/jira/browse/FLINK-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann updated FLINK-6434:
---------------------------------
Comment: was deleted
(was: Thanks for reporting the issue. I think the best way to solve the problem is to check whether we can complete the pending request future. If this is not the case, then we should release the {{SimpleSlot}} and add the {{AllocatedSlot}} to the set of {{availableSlots}} instead of moving it to {{allocatedSlots}}.)
> 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)