Github user michellemay commented on the pull request:
https://github.com/apache/spark/pull/8105#issuecomment-129944335
As I explain, the problem arise when log4j gets initialized before
MutableURLClassLoader gets set on the thread context by spark in the main
method.
When parsing arguments, ShutdownManager is statically initialized by a call
to addShutdownHook in the Utils class. This trigger an initialization of
log4j. When moving shutdown hook things to a separate class, it gets lazily
initialized later on.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
