Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.6.0, 1.7.0
Description
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.
Attachments
Issue Links
- is depended upon by
-
FLINK-10142 Reduce synchronization overhead for credit notifications
- Resolved
- links to