ASF GitHub Bot commented on FLINK-8694:

Github user NicoK commented on the issue:

    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

Reply via email to