[
https://issues.apache.org/jira/browse/FLINK-37769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17949951#comment-17949951
]
david radley commented on FLINK-37769:
--------------------------------------
I wonder is there additional information from the job we can get, before we
restart it that would be help in the message, to add further clarity as to the
cause of the unhealthy job?
> 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)
