Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16573
Since the log level is not stored in Spark, we cannot recover the correct
level if the user just uses
`org.apache.log4j.Logger.getRootLogger().setLevel(l)` to set. In addition, if I
use `org.apache.log4j.Logger.getRootLogger().setLevel(l)` to set the level in
my code, but Spark will change it after recovery, I would be very surprised.
Hence, I suggest to not fix this one.
---
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]