[
https://issues.apache.org/jira/browse/FLINK-21510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21510:
-----------------------------------
Labels: auto-unassigned reactive stale-major (was: auto-unassigned
reactive)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: auto-unassigned, reactive, stale-major
>
> 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)
