Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/16866
@zsxwing, as described in the PR description, if we throw an `IOException`
subclass from this then we need to modify `RetryingBlockFetcher` to have
special-case handling of `InterruptedIOException`:
> An alternative approach would be to wrap `InterruptedException` into
`IOException` in order to avoid having to change interfaces. The problem with
this approach is that the `network-shuffle` project's `RetryingBlockFetcher`
code treats `IOExceptions` as transitive failures when deciding whether to
retry fetches, so throwing a wrapped `IOException` might cause an interrupted
shuffle fetch to be retried, further prolonging the lifetime of a cancelled
zombie task.
---
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
