flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From uce <...@git.apache.org>
Subject [GitHub] flink pull request: [FLINK-2134] Close Netty channel via CloseRequ...
Date Wed, 03 Jun 2015 16:53:16 GMT
GitHub user uce opened a pull request:


    [FLINK-2134] Close Netty channel via CloseRequest msg

    The failing `SuccessAfterNetworkBuffersFailureITCase` discovered a race between sending
backwards events (e.g. from sync task to iteration head task) and closing the TCP channel.
The close overtook outstanding backwards task events. This change guarnatees that it is in
order by sending a explicit close msg.
    (I've also tried other approaches, but this struck me as the simplest solution.)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/uce/incubator-flink event-deadlock-2134

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #773
commit 6a4dcd0d4866ba16c432d15de25df7c161c894b7
Author: Ufuk Celebi <uce@apache.org>
Date:   2015-06-03T16:41:40Z

    [FLINK-2134] Close Netty channel via CloseRequest msg


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message