[
https://issues.apache.org/jira/browse/FLINK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-10146:
-----------------------------------
Labels: auto-unassigned stale-major (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> numBuffersOut not updated properly
> ----------------------------------
>
> Key: FLINK-10146
> URL: https://issues.apache.org/jira/browse/FLINK-10146
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Metrics, Runtime / Network
> Affects Versions: 1.5.3, 1.6.1, 1.7.0
> Reporter: Nico Kruber
> Priority: Major
> Labels: auto-unassigned, stale-major
>
> We only enqueue a {{BufferConsumer}} once into the result (sub)partition but
> Netty may draw and send parts of it independently. {{numBuffersOut}} is,
> however, only increased when a new buffer is retrieved from the buffer pool,
> not when an actual buffer is sent via Netty. This metric is thus wrong.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
