Details

      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

            Activity

              People

              • Assignee:
                NicoK Nico Kruber
                Reporter:
                NicoK Nico Kruber
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: