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

Posted to issues@flink.apache.org by "Matyas Orhidi (Jira)" <ji...@apache.org> on 2022/05/02 08:48:00 UTC

[jira] [Updated] (FLINK-27468) Observing JobManager deployment. Previous status: MISSING

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

Matyas Orhidi updated FLINK-27468:
----------------------------------
    Description: The operator keeps looping if the JM Deployment gets deleted ( and probably when the job is in terminal Flink state such as FAILED). We need to agree on how to handle such cases and fix it.  (was: The operator keeps looping if the K8s deployment gets deleted ( and probably when the job is in terminal Flink state such as FAILED). We need to agree on how to handle such cases and fix it.)

> Observing JobManager deployment. Previous status: MISSING
> ---------------------------------------------------------
>
>                 Key: FLINK-27468
>                 URL: https://issues.apache.org/jira/browse/FLINK-27468
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-0.1.0
>            Reporter: Matyas Orhidi
>            Priority: Major
>
> The operator keeps looping if the JM Deployment gets deleted ( and probably when the job is in terminal Flink state such as FAILED). We need to agree on how to handle such cases and fix it.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)