You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2020/12/17 15:18:01 UTC
[jira] [Closed] (FLINK-20605) DeclarativeSlotManager crashes if
slot allocation notification is processed out-of-order
[ https://issues.apache.org/jira/browse/FLINK-20605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-20605.
------------------------------------
Resolution: Fixed
master: 5cabecb0f7b7ad25036badca40500782eacef848
> DeclarativeSlotManager crashes if slot allocation notification is processed out-of-order
> ----------------------------------------------------------------------------------------
>
> Key: FLINK-20605
> URL: https://issues.apache.org/jira/browse/FLINK-20605
> Project: Flink
> Issue Type: Improvement
> 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
>
>
> It is possible that a notification from a task executor about a slot being allocated can be processed after that very task executor has unregistered itself from the resource manager.
> As a result we run into an exception when trying to mark this slot as allocated, because it no longer exists and a precondition catches this case.
> We could solve this by checking in {{DeclarativeResourceManager#allocateSlot}} whether the task executor we received the acknowledge from is still registered.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)