You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2021/09/01 08:01:00 UTC
[jira] [Commented] (FLINK-21510) ExecutionGraph metrics collide on
restart
[ https://issues.apache.org/jira/browse/FLINK-21510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17407938#comment-17407938 ]
Robert Metzger commented on FLINK-21510:
----------------------------------------
How much effort would it be fix this issue?
These are some important metrics, that are missing when using Adaptive Scheduler.
> ExecutionGraph metrics collide on restart
> -----------------------------------------
>
> Key: FLINK-21510
> URL: https://issues.apache.org/jira/browse/FLINK-21510
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Chesnay Schepler
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned, reactive
>
> The ExecutionGraphBuilder registers several metrics directly on the JobManagerJobMetricGroup, which are never cleaned up.
> These include upTime/DownTime/restartingTime as well as various checkpointing metrics (see the CheckpointStatsTracker for details; examples are number of checkpoints, checkpoint sizes etc).
> When the AdaptiveScheduler re-creates the EG these will collide with metrics of prior attempts.
> Essentially we either need to create a separate metric group that we pass to the EG or refactor the metrics to be based on some mutable EG reference.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)