Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/21356
@zsxwing Imran knows more since he debugged it, but I see a lot of code
like this in Hadoop libraries:
```
try { ... } catch (InterruptedException ie) {
// log or something
Thread.currentThread().interrupt();
}
```
Which could cause things like this. I don't know what would cause the
exception in the first place, but the fact that the library is propagating the
interrupt to the caller explains why Spark is seeing it in one of its own calls.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
