You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yangze Guo (Jira)" <ji...@apache.org> on 2024/02/19 02:26:00 UTC

[jira] [Assigned] (FLINK-34434) DefaultSlotStatusSyncer doesn't complete the returned future

     [ https://issues.apache.org/jira/browse/FLINK-34434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yangze Guo reassigned FLINK-34434:
----------------------------------

    Assignee: Yangze Guo

> DefaultSlotStatusSyncer doesn't complete the returned future
> ------------------------------------------------------------
>
>                 Key: FLINK-34434
>                 URL: https://issues.apache.org/jira/browse/FLINK-34434
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.17.2, 1.19.0, 1.18.1, 1.20.0
>            Reporter: Matthias Pohl
>            Assignee: Yangze Guo
>            Priority: Major
>
> When looking into FLINK-34427 (unrelated), I noticed an odd line in [DefaultSlotStatusSyncer:155|https://github.com/apache/flink/blob/15fe1653acec45d7c7bac17071e9773a4aa690a4/flink-runtime/src/main/java/org/apache/flink/runtime/resourcemanager/slotmanager/DefaultSlotStatusSyncer.java#L155] where we complete a future that should be already completed (because the callback is triggered after the {{requestFuture}} is already completed in some way. Shouldn't we complete the {{returnedFuture}} instead?
> I'm keeping the priority at {{Major}} because it doesn't seem to have been an issue in the past.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)