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

Posted to issues@flink.apache.org by "Aitozi (Jira)" <ji...@apache.org> on 2022/03/23 03:29:00 UTC

[jira] [Closed] (FLINK-26807) The batch job not work well with Operator

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

Aitozi closed FLINK-26807.
--------------------------
    Resolution: Duplicate

> The batch job not work well with Operator
> -----------------------------------------
>
>                 Key: FLINK-26807
>                 URL: https://issues.apache.org/jira/browse/FLINK-26807
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Kubernetes Operator
>            Reporter: Aitozi
>            Priority: Major
>
> When I test the batch job or finite streaming job, the flinkdep will be an orphaned resource and keep listing job after job finished. Because the JobManagerDeploymentStatus will not be sync again.
> I think we should sync the global terminated status from the application job, and do the clean up work for the flinkdep resource



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