You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/10/12 10:11:00 UTC
[jira] [Resolved] (FLINK-9943) Support
TaskManagerMetricQueryServicePaths msg in JobManager Actor
[ https://issues.apache.org/jira/browse/FLINK-9943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann resolved FLINK-9943.
----------------------------------
Resolution: Won't Do
Fix Version/s: (was: 1.7.0)
> 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
>
> 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)