[jira] [Resolved] (FLINK-10141) Reduce lock contention introduced with 1.5

["Nico Kruber (JIRA)" <ji...@apache.org>]

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

Nico Kruber resolved FLINK-10141.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.4
                   1.7.0
                   1.6.1

Fixed via:
- master: 6c7603724be6c146cfc8019b77b60236d1d3d582
- release-1.6: b3dadd6fe3fa3e163ec9e25bff52c642e91f683f
- release-1.5: 0d5f75e9a005a32dcff1b545f146064bd6ce66e9

> Reduce lock contention introduced with 1.5
> ------------------------------------------
>
>                 Key: FLINK-10141
>                 URL: https://issues.apache.org/jira/browse/FLINK-10141
>             Project: Flink
>          Issue Type: Bug
>          Components: Network
>    Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.6.0, 1.7.0
>            Reporter: Nico Kruber
>            Assignee: Nico Kruber
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.6.1, 1.7.0, 1.5.4
>
>
> With the changes around introducing credit-based flow control as well as the low latency changes, unfortunately, we also introduced some lock contention on {{RemoteInputChannel#bufferQueue}} and {{RemoteInputChannel#receivedBuffers}} as well as asking for queue sizes when the only thing we need is whether it is empty or not.
> This was observed as a high idle CPU load with no events in the stream but only watermarks (every 500ms) and many slots on a single machine.



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