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

Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2019/04/30 08:04:00 UTC

[jira] [Closed] (FLINK-12199) Refactor IOMetrics to not distinguish between local/remote in/out bytes

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

Chesnay Schepler closed FLINK-12199.
------------------------------------
    Resolution: Fixed

master: f98a7a8558deb155c6a20bb7b9687feb949514f7

> Refactor IOMetrics to not distinguish between local/remote in/out bytes
> -----------------------------------------------------------------------
>
>                 Key: FLINK-12199
>                 URL: https://issues.apache.org/jira/browse/FLINK-12199
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Network
>            Reporter: Andrey Zagrebin
>            Assignee: zhijiang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> At the moment we have numBytesInLocal/numBytesInRemote in IOMetrics but in the actual usage we just always sum them up. As local/remote is the detail of shuffle service implementation, we can merge the local/remote metrics into one and increment it later in Task instead of remote/local channels in network internals.



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