[
https://issues.apache.org/jira/browse/FLINK-37564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora updated FLINK-37564:
-------------------------------
Description:
Currently the Flink operator does not trigger any events when the job goes
through a regular failover, however this would be very valuable for the user.
We should query the exception list in case of restarts and trigger events.
was:
Currently the Flink operator uses the jobResults to fetch the exceptions but
that has a severe limitation that it returns the serialized exception which in
most cases cannot be deserialized by the operator.
Instead we should replace this logic using the exception history JM endpoint
which returns string based exception info / stack traces
Summary: Trigger warning event when job fails to provide visibility
(was: Rework job error fetching to use Exception history instead of JobResults)
> Trigger warning event when job fails to provide visibility
> ----------------------------------------------------------
>
> Key: FLINK-37564
> URL: https://issues.apache.org/jira/browse/FLINK-37564
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Rodrigo Meneses
> Priority: Major
>
> Currently the Flink operator does not trigger any events when the job goes
> through a regular failover, however this would be very valuable for the user.
> We should query the exception list in case of restarts and trigger events.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
