Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9946#issuecomment-173300190
I'm not against this change; in fact, this is already the current behavior
in healthy YARN installs (since YARN will kill your container). I just wanted
the change description to be more descriptive of the underlying reason why the
exit being explicitly added.
I also don't buy the existence of any valid user case for a user thread to
block container exit, exactly for the reason above.
---
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
