[
https://issues.apache.org/jira/browse/FLINK-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614772#comment-15614772
]
ASF GitHub Bot commented on FLINK-4733:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/2616
The `CoordinatorShutdownTest` can't be fixed with a cast. This test assumes
that the actual ExecutionGraph is still available when a job is finished since
it tries to access the CheckpointCoordinator within. This however no longer
works; finished jobs are immediately archived, and the archived version does
not contain the CheckpointCoordinator.
A possible fix is to not let the job fail immediately but block him, ask
for the ExecutionGraph while being blocked (which, since the job is still
running actually returns the runtime ExecutionGraph) and store the reference,
and then let the job fail.
> Port WebFrontend to new metric system
> -------------------------------------
>
> Key: FLINK-4733
> URL: https://issues.apache.org/jira/browse/FLINK-4733
> Project: Flink
> Issue Type: Improvement
> Components: Metrics, TaskManager, Webfrontend
> Affects Versions: 1.1.2
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Fix For: 1.2.0
>
>
> While the WebFrontend has access to the metric system it still relies on
> older code in some parts.
> The TaskManager metrics are still gathered using the Codahale library and
> send with the heartbeats.
> Task related metrics (numRecordsIn etc) are still gathered using
> accumulators, which are accessed through the execution graph.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
