You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gary Yao (Jira)" <ji...@apache.org> on 2019/12/17 12:52:00 UTC
[jira] [Closed] (FLINK-15169) Errors happen in the scheduling of
DefaultScheduler are not shown in WebUI
[ https://issues.apache.org/jira/browse/FLINK-15169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Yao closed FLINK-15169.
----------------------------
Resolution: Fixed
1.10:
bb8971e9d699249e835e0373009e27251c6a7dd0
1bf8e89aff64c930b4df0ec99bdcb4e698305465
master:
6ed64abab3c3a041fc65ae954ddb35e026c1e94f
0186e1059db0e7829d6fb57d8b681686bf9b0e43
> Errors happen in the scheduling of DefaultScheduler are not shown in WebUI
> --------------------------------------------------------------------------
>
> Key: FLINK-15169
> URL: https://issues.apache.org/jira/browse/FLINK-15169
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> WebUI relies on {{ExecutionGraph#failureInfo}} and {{Execution#failureCause}} to generate error info (via {{JobExceptionsHandler#createJobExceptionsInfo}}).
> Errors happen in the scheduling of DefaultScheduler are not recorded into those fields, thus cannot be shown to users in WebUI (nor via REST queries).
> To solve it,
> 1. global failures should be recorded into {{ExecutionGraph#failureInfo}}, via {{ExecutionGraph#initFailureCause}} which can be exposed as {{SchedulerBase#initFailureCause}}.
> 2. for task failures, one solution I can think of is to avoid invoking {{DefaultScheduler#handleTaskFailure}} directly on scheduler's internal failures. Instead, we can introduce {{ExecutionVertexOperations#fail(ExecutionVertex)}} to hand the error to {{ExecutionVertex}} as a common failure.
> cc [~gjy]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)