Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.6.0, 1.7.0
Description
With the re-design of the record writer interaction with the result(sub)partitions, flush requests can currently pile up in these scenarios:
- a previous flush request has not been completely handled yet and/or is still enqueued or
- the network stack is still polling from this subpartition and doesn't need a new notification
These lead to increased notifications in low latency settings (low output flusher intervals) which can be avoided.
Attachments
Issue Links
- links to