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

Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/06/09 10:53:00 UTC

[jira] [Closed] (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 ]

Gyula Fora closed FLINK-27497.
------------------------------
    Resolution: Fixed

merged to main 18fdd7e8cd870bac7763a79d0af99c64d4e181a7

> 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
>            Reporter: Gyula Fora
>            Assignee: Aitozi
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: kubernetes-operator-1.1.0
>
>
> 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)