You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2022/03/19 14:07:00 UTC

[jira] [Resolved] (FLINK-26690) DefaultJobGraphStore.globalCleanup does not trigger the cleanup when retrying the cleanup after a failover

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

Matthias Pohl resolved FLINK-26690.
-----------------------------------
    Resolution: Fixed

master: 89bfd3994c18e770cae4d4c98dffb8aefd808a21
1.15: 3966744a18d9f0e408474969c1f61ea43c8b41d5

> DefaultJobGraphStore.globalCleanup does not trigger the cleanup when retrying the cleanup after a failover
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-26690
>                 URL: https://issues.apache.org/jira/browse/FLINK-26690
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.15.0
>            Reporter: Matthias Pohl
>            Assignee: Matthias Pohl
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> The {{DefaultJobGraphStore}} does not get the JobGraph of a dirty globally-terminated job after failover anymore because the job is not going to be recovered. The globalCleanup checks the addedJobs still, which is not necessary but prevents the cleanup in that case.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)