[
https://issues.apache.org/jira/browse/FLINK-27497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533416#comment-17533416
]
Aitozi edited comment on FLINK-27497 at 5/8/22 6:39 AM:
--------------------------------------------------------
I think it will be a very good improvement, I would like to give a try on this
was (Author: aitozi):
I think it will be very useful improvements, I would like to give a try on this
> 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
> Priority: Critical
>
> 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)
