[
https://issues.apache.org/jira/browse/FLINK-11603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler closed FLINK-11603.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
master: 6e8a3f312919f8f088c132b13b727cb2188eacb5
> Port MetricQueryService to RpcEndpoint
> --------------------------------------
>
> Key: FLINK-11603
> URL: https://issues.apache.org/jira/browse/FLINK-11603
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Reporter: TisonKun
> Assignee: TisonKun
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
