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] [Updated] (FLINK-11603) Port the MetricQueryService to the new RpcEndpoint
Date Thu, 07 Mar 2019 12:29:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-11603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

ASF GitHub Bot updated FLINK-11603:
-----------------------------------
    Labels: pull-request-available  (was: )

> Port the MetricQueryService to the new 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
>
> 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)

Mime
View raw message