You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "TisonKun (JIRA)" <ji...@apache.org> on 2019/02/14 00:22:00 UTC

[jira] [Created] (FLINK-11603) Ported the MetricQueryService to the new RpcEndpoint

TisonKun created FLINK-11603:
--------------------------------

             Summary: Ported the MetricQueryService to the new RpcEndpoint
                 Key: FLINK-11603
                 URL: https://issues.apache.org/jira/browse/FLINK-11603
             Project: Flink
          Issue Type: Improvement
          Components: Metrics
            Reporter: TisonKun
            Assignee: TisonKun


Given that a series TODO mention {{This is a temporary hack until we have ported the MetricQueryService to the new RpcEndpoint}}, I'd like to give it a try to implement the RpcEndpoint version of MetricQueryService.

Basically, port {{onRecieve}} to 
1. {{addMetric(metricName, metric, group)}}
2. {{removeMetric(metric)}}
3. {{createDump()}}

And then adjust tests and replace {{metricServiceQueryPath}} with a corresponding {{RpcGateway}}.

I'd like to learn that if the statement if true --- when we call a Runnable/Callable with runAsync/callAsync, then the Runnable/Callable is running in the main thread of the underlying RPC service, specifically, in the actor thread?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)