Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/4008#issuecomment-69658255
Oh, and to provide a little more context, the reason that we're able to
cancel most tasks even though we don't perform thread interrupts is that we
have an
[InterruptibleIterator](https://github.com/uncleGen/spark/blob/master-clean-150112/core/src/main/scala/org/apache/spark/InterruptibleIterator.scala)
class that causes canceled tasks to throw exceptions when they try to consume
their next element of input. That doesn't seem to take effect here, though,
because our receiver task doesn't consume any input.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
