You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Nico Kruber (JIRA)" <ji...@apache.org> on 2018/07/04 22:36:00 UTC

[jira] [Created] (FLINK-9755) Exceptions in RemoteInputChannel#notifyBufferAvailable() are not propagated to the responsible thread

Nico Kruber created FLINK-9755:
----------------------------------

             Summary: Exceptions in RemoteInputChannel#notifyBufferAvailable() are not propagated to the responsible thread
                 Key: FLINK-9755
                 URL: https://issues.apache.org/jira/browse/FLINK-9755
             Project: Flink
          Issue Type: Bug
          Components: Network
    Affects Versions: 1.5.0
            Reporter: Nico Kruber
            Assignee: Nico Kruber
             Fix For: 1.6.0, 1.5.2


The credit-based flow control implementation of RemoteInputChannel#notifyBufferAvailable() does not forward errors (like the {{IllegalStateException}}) to the thread that is being notified. The calling code at {{LocalBufferPool#recycle}}, however, relies on the callback forwarding errors and completely ignores any failures.

Therefore, we could end up with a program waiting forever for the callback and not even a failure message in the logs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)