[
https://issues.apache.org/jira/browse/FLINK-9943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561128#comment-16561128
]
ASF GitHub Bot commented on FLINK-9943:
---------------------------------------
chuanlei commented on issue #6429: [FLINK-9943] Support
TaskManagerMetricQueryServicePaths msg in JobManager Actor
URL: https://github.com/apache/flink/pull/6429#issuecomment-408682620
cc @zentol could you please have a look for this pr?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Support TaskManagerMetricQueryServicePaths msg in JobManager Actor
> ------------------------------------------------------------------
>
> Key: FLINK-9943
> URL: https://issues.apache.org/jira/browse/FLINK-9943
> Project: Flink
> Issue Type: New Feature
> Components: Core
> Affects Versions: 1.5.0, 1.5.1
> Reporter: Chuanlei Ni
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
>
> The reasons are as follows
> # AkkaJobManagerGateway wraps jm actor ref to support such functionality by
> request RegisteredTaskManagers firstly and request task manager actor to get
> metric query service path one by one. the procedure above is resource-wasted.
> It will be more efficient if we support this functionality in the jm actor
> # we can expose flink metric system directly to external system (such as
> flink client and the like) to support more features in future. For now,
> metric system has been exposed partially because Instance can not (and should
> not) be transfered remotely. This feature will make metrics exposure
> consistent.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
