[
https://issues.apache.org/jira/browse/FLINK-37769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17949957#comment-17949957
]
Gyula Fora commented on FLINK-37769:
------------------------------------
I think the point here would be to simply include why the Operator thought the
job was unhealthy. Adding extra info from the job is probably out of scope here
> Include cause in event when Restarting unhealthy job
> ----------------------------------------------------
>
> Key: FLINK-37769
> URL: https://issues.apache.org/jira/browse/FLINK-37769
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Daren Wong
> Priority: Major
>
> When the kubernetes operator restarts unhealthy jobs due to any reason an
> event is triggered with the following message:
> "Restarting unhealthy job"
> We should extend this message to include the cause why the job was determined
> to be unhealthy:
> "Restarting unhealthy job: X restarts within Y minutes"
> "Restarting unhealthy job: No checkpoint taken within X minutes"
> etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)