You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Andrey Zagrebin (JIRA)" <ji...@apache.org> on 2019/05/15 09:10:00 UTC

[jira] [Closed] (FLINK-12202) Consider introducing batch metric register in NetworkEnviroment

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

Andrey Zagrebin closed FLINK-12202.
-----------------------------------
    Resolution: Won't Fix

we can register metrics with NetworkEnviroment.createPartitions/Gates atm.

> Consider introducing batch metric register in NetworkEnviroment
> ---------------------------------------------------------------
>
>                 Key: FLINK-12202
>                 URL: https://issues.apache.org/jira/browse/FLINK-12202
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Metrics, Runtime / Network
>            Reporter: Andrey Zagrebin
>            Assignee: zhijiang
>            Priority: Major
>
> As we have some network specific metrics registered in TaskIOMetricGroup (In/OutputBuffersGauge, In/OutputBufferPoolUsageGauge), we can introduce batch metric registering in NetworkEnviroment.registerMetrics(ProxyMetricGroup, partitions, gates), where task passes its TaskIOMetricGroup into ProxyMetricGroup. This way we could break a tie between task and NetworkEnviroment. TaskIOMetricGroup.initializeBufferMetrics, In/OutputBuffersGauge, In/OutputBufferPoolUsageGauge could be moved into NetworkEnviroment.registerMetrics and network code.



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