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

Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2021/01/15 10:31:00 UTC

[jira] [Assigned] (FLINK-10147) numBytesOut metric lagging behind

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

Robert Metzger reassigned FLINK-10147:
--------------------------------------

    Assignee:     (was: boshu Zheng)

> numBytesOut metric lagging behind
> ---------------------------------
>
>                 Key: FLINK-10147
>                 URL: https://issues.apache.org/jira/browse/FLINK-10147
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Metrics, Runtime / Network
>    Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.7.0
>            Reporter: Nico Kruber
>            Priority: Minor
>
> Since the low-latency changes in the network stack, {{numBytesOut}} is only updated whenever a new buffer is retrieved from the buffer pool. We do, however, keep the old buffer enqueued until all its bytes have been written. In low load scenarios this may thus seem like we do not send any bytes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)