flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7876) Register TaskManagerMetricGroup under ResourceID instead of InstanceID
Date Wed, 01 Nov 2017 10:33:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16233900#comment-16233900

ASF GitHub Bot commented on FLINK-7876:

Github user tillrohrmann commented on a diff in the pull request:

    --- Diff: flink-runtime/src/test/scala/org/apache/flink/runtime/testingUtils/TestingCluster.scala
    @@ -42,7 +42,8 @@ import org.apache.flink.runtime.jobmanager.{JobManager, MemoryArchivist,
     import org.apache.flink.runtime.leaderelection.LeaderElectionService
     import org.apache.flink.runtime.messages.JobManagerMessages
     import org.apache.flink.runtime.messages.JobManagerMessages._
    -import org.apache.flink.runtime.metrics.MetricRegistry
    +import org.apache.flink.runtime.metrics.MetricRegistryImpl
    --- End diff --
    Will remove it.

> Register TaskManagerMetricGroup under ResourceID instead of InstanceID
> ----------------------------------------------------------------------
>                 Key: FLINK-7876
>                 URL: https://issues.apache.org/jira/browse/FLINK-7876
>             Project: Flink
>          Issue Type: Improvement
>          Components: Metrics
>    Affects Versions: 1.4.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Minor
>              Labels: flip-6
> Currently, the {{TaskManager}} registers the {{TaskManagerMetricGroup}} under its {{InstanceID}}
and thereby binding its metrics effectively to the lifetime of its registration with the {{JobManager}}.
This has also implications how the REST handler retrieve the TaskManager metrics, namely by
its {{InstanceID}}.
> I would actually propose to register the {{TaskManagerMetricGroup}} under the {{TaskManager}}/{{TaskExecutor}}
{{ResourceID}} which is valid over the whole lifetime of the {{TaskManager}}/{{TaskExecutor}}.
That way we would also be able to query metrics independent of the connection status to the

This message was sent by Atlassian JIRA

View raw message