[ https://issues.apache.org/jira/browse/FLINK-10331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nico Kruber resolved FLINK-10331. --------------------------------- Resolution: Fixed Fix Version/s: 1.5.5 1.6.2 1.7.0 Fixed via: - release-1.5: 16ea186fef3ac7eee8679f8e87132313508573b3 - release-1.6: ef192266e94c088b05d611e25165b7efdb0585d8 - master: a9e5f70515a3cbad7e776b9248e841f6c81c9b7a > Fix unnecessary flush requests to the network stack > --------------------------------------------------- > > Key: FLINK-10331 > URL: https://issues.apache.org/jira/browse/FLINK-10331 > Project: Flink > Issue Type: Sub-task > 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.7.0, 1.6.2, 1.5.5 > > > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)