[ 
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-deprioritized-major auto-unassigned stale-minor  (was: 
auto-deprioritized-major 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 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, 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: Minor
>              Labels: auto-deprioritized-major, auto-unassigned, stale-minor
>
> 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.20.1#820001)

Reply via email to