Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/9946#issuecomment-161308748
Well the users shouldn't have been using non-daemon threads in the first
place, they spawned them while a task was running and then never cleaned them
up. We asked them to change that. I can't think of any scenarios where the
user should be relying on anything running past when the users task code exits
as it would just be a natural race condition. the task finishes and the driver
could kill the container, it could finish the app and yarn could kill the
container, etc. whatever they are doing may or may not finish anyway.
---
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
