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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/06/07 10:12:00 UTC

[jira] [Updated] (FLINK-27497) Track terminal job states in the observer

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

ASF GitHub Bot updated FLINK-27497:
-----------------------------------
    Labels: pull-request-available  (was: )

> Track terminal job states in the observer
> -----------------------------------------
>
>                 Key: FLINK-27497
>                 URL: https://issues.apache.org/jira/browse/FLINK-27497
>             Project: Flink
>          Issue Type: New Feature
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.0.0
>            Reporter: Gyula Fora
>            Assignee: Aitozi
>            Priority: Critical
>              Labels: pull-request-available
>
> With the improvements in FLINK-27468 Flink 1.15 app clusters will not be shut down in case of terminal job states (failed, finished) etc.
> It is important to properly handle these states and let the user know about it.
> We should always trigger events, and for terminally failed jobs record the error information in the FlinkDeployment status.



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