[
https://issues.apache.org/jira/browse/FLINK-27497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537304#comment-17537304
]
Aitozi commented on FLINK-27497:
--------------------------------
[~gyfora] Thanks for your remind.
Besides I have question when I test this functionality. I found that the
{{execution.submit-failed-job-on-application-error}} seems only work for the
job enabled HA, If it's disabled, we can not get error from the application I
think. But I don't quite understand why only HA job can supported
> 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
>
> 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)
