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 Mon, 30 Oct 2017 10:46:02 GMT

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

ASF GitHub Bot commented on FLINK-7876:
---------------------------------------

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

    https://github.com/apache/flink/pull/4872#discussion_r147666537
  
    --- Diff: flink-runtime/src/main/java/org/apache/flink/runtime/resourcemanager/ResourceManagerGateway.java
---
    @@ -166,4 +169,12 @@ void notifySlotAvailable(
     	 * @return Future containing the resource overview
     	 */
     	CompletableFuture<ResourceOverview> requestResourceOverview(@RpcTimeout Time timeout);
    +
    +	/**
    +	 * Requests the paths for the TaskManager's {@link MetricQueryService} to query.
    +	 *
    +	 * @param timeout for the asynchronous operation
    +	 * @return Future containing the collection of instance ids and the corresponding metric
query service path
    --- End diff --
    
    resource ids?


> 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
{{JobManager}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message