[
https://issues.apache.org/jira/browse/FLINK-20833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17265123#comment-17265123
]
Robert Metzger commented on FLINK-20833:
----------------------------------------
Thanks for your summary.
I haven't understood why you chose "ExecutionFailureClassifier" as the
interface name? I wonder if "ExceptionListener" is a more suitable name.
Secondly, I don't understand why we need a default no-op operation.
Can't we just call the listener only if it's set?
How do you plan to load a custom ExceptionListener/ExecutionFailureClassifier
implementation? Are users supposed to put a jar file with the implementation
into Flink's classpath?
You mentioned that you want to send metrics in your own implementation: Do you
want to use Flink's metrics system, or will your listener just establish a
connection to a metrics system to report them there?
> Expose pluggable interface for exception analysis and metrics reporting in
> Execution Graph
> -------------------------------------------------------------------------------------------
>
> Key: FLINK-20833
> URL: https://issues.apache.org/jira/browse/FLINK-20833
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.12.0
> Reporter: Zhenqiu Huang
> Priority: Minor
>
> For platform users of Apache flink, people usually want to classify the
> failure reason( for example user code, networking, dependencies and etc) for
> Flink jobs and emit metrics for those analyzed results. So that platform can
> provide an accurate value for system reliability by distinguishing the
> failure due to user logic from the system issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
