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/18 17:08:00 UTC
[jira] [Resolved] (FLINK-10602) Run MetricFetcher in metrics
ActorSystem
[ https://issues.apache.org/jira/browse/FLINK-10602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann resolved FLINK-10602.
-----------------------------------
Resolution: Fixed
Fixed via https://github.com/apache/flink/commit/f6a7100507c4d6eda25c10618f0ad028ffef32d8
> Run MetricFetcher in metrics ActorSystem
> ----------------------------------------
>
> Key: FLINK-10602
> URL: https://issues.apache.org/jira/browse/FLINK-10602
> Project: Flink
> Issue Type: Sub-task
> Components: Metrics
> Affects Versions: 1.7.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
>
> After letting the {{MetricQueryService}} run into a separate {{ActorSystem}}, we should also let the {{MetricFetcher}} use the same {{ActorSystem}} to fetch the metrics. That way it will be possible to configure the metric {{ActorSystem}} different from the {{RpcService}} {{ActorSystem}} (e.g. different frame size).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)