[
https://issues.apache.org/jira/browse/FLINK-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372994#comment-16372994
]
ASF GitHub Bot commented on FLINK-8694:
---------------------------------------
Github user NicoK commented on the issue:
https://github.com/apache/flink/pull/5557
While this may certainly "fix" the problem with the flush-always setting, I
don't like the approach of ignoring the problem that some `notifyDataAvailable`
calls are ignored and we have to wait for the next flush to appear. We should
rather fix the cause and not hide the problem (we currently have no test that
shows the problem!).
> Make notifyDataAvailable call reliable
> --------------------------------------
>
> Key: FLINK-8694
> URL: https://issues.apache.org/jira/browse/FLINK-8694
> Project: Flink
> Issue Type: Sub-task
> Reporter: Piotr Nowojski
> Assignee: Piotr Nowojski
> Priority: Major
>
> After FLINK-8591
> org.apache.flink.runtime.io.network.netty.SequenceNumberingViewReader#notifyDataAvailable
> (and the same for Credit base flow control) due to race condition can be
> sometimes ignored.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
