[
https://issues.apache.org/jira/browse/FLINK-21439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348835#comment-17348835
]
John Phelan commented on FLINK-21439:
-------------------------------------
No worries [~mapohl] . It seems to still be very much a moving target. I can
see what you meant and how you're looking at global failures now.
I like your abstraction layer of [flink/FailureHandlingResultSnapshot.java at
317687b20901151165db39365e3634b002c70d3e · apache/flink
(github.com)|https://github.com/apache/flink/blob/317687b20901151165db39365e3634b002c70d3e/flink-runtime/src/main/java/org/apache/flink/runtime/scheduler/exceptionhistory/FailureHandlingResultSnapshot.java#L59]
Do you think we could add another static method to
{{FailureHandlingResultSnapshot}} to accomplish the same result as was possible
with the previous:
{code:java}
exceptionHistoryEntryExtractor.extractLocalFailure(
executionGraph.getAllVertices(),
executionVertexID,
verticesToRestart);
{code}
> Adaptive Scheduler: Add support for exception history
> -----------------------------------------------------
>
> Key: FLINK-21439
> URL: https://issues.apache.org/jira/browse/FLINK-21439
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.13.0
> Reporter: Matthias
> Assignee: John Phelan
> Priority: Major
> Labels: pull-request-available, reactive
> Time Spent: 3h
> Remaining Estimate: 0h
>
> {{SchedulerNG.requestJob}} returns an {{ExecutionGraphInfo}} that was
> introduced in FLINK-21188. This {{ExecutionGraphInfo}} holds the information
> about the {{ArchivedExecutionGraph}} and exception history information.
> Currently, it's a list of {{ErrorInfos}}. This might change due to ongoing
> work in FLINK-21190 where we might introduced a wrapper class with more
> information on the failure.
> The goal of this ticket is to implement the exception history for the
> {{AdaptiveScheduler}}, i.e. collecting the exceptions that caused restarts.
> This collection of failures should be forwarded through
> {{SchedulerNG.requestJob}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
