GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/746
Fix handling of receiver and sender task failures
**Sender task failures** (1955)
- Produced result partition becomes erroneous with a ProducerFailedException
- Receiver cancels itself when encountering the ProducerFailedException by
throwing an instance of CancelTaskException (it may also be cancelled by the
JobManager if that call is faster than the detection of the failed producer)
- Reference to Netty channel is released
**Receiver task failures** (1958)
- Sender keeps going. May be back-pressured when no receiver pulls the data
any more.
- Sender may be cancelled by JobManager
- Partition stays sane
- Reference to Netty channel is released
- Transfer are canceled by a cancel message (receiver to sender)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uce/incubator-flink receiver_fails-1958
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/746.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #746
commit 96e29bb01f9b78ad4de3dc048021e40f12d5fac8
Author: Ufuk Celebi u...@apache.org
Date: 2015-05-28T09:45:52Z
[FLINK-1954] [FLINK-1958] [runtime] Cancel transfers of failed receiver
tasks
commit 16b718e02726aaa0eeaf63531b63d2b341a162e1
Author: Ufuk Celebi u...@apache.org
Date: 2015-05-28T12:58:31Z
[FLINK-1954] [FLINK-1955] [runtime] Set task failure cause for produced
result partitions
commit 1825e09655a34271ee7ab91735a927c3784f008f
Author: Ufuk Celebi u...@apache.org
Date: 2015-05-28T13:57:39Z
[runtime] Fix uncaught exception in Netty server pipeline
commit 20f208bd3020b9c9e600be7687ac2da5443fd676
Author: Ufuk Celebi u...@apache.org
Date: 2015-05-29T08:54:16Z
[runtime] Rename internal field of Netty error message
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
