Kousuke Saruta created SPARK-30167:
--------------------------------------
Summary: Log4j configuration for REPL can't override the root
logger properly.
Key: SPARK-30167
URL: https://issues.apache.org/jira/browse/SPARK-30167
Project: Spark
Issue Type: Bug
Components: Spark Shell
Affects Versions: 3.0.0
Reporter: Kousuke Saruta
Assignee: Kousuke Saruta
SPARK-11929 enabled REPL's log4j configuration to override root logger but
SPARK-26753 seems to have broken the feature.
You can see one example when you modifies the default log4j configuration like
as follows.
{code:java}
# Change the log level for rootCategory to DEBUG
log4j.rootCategory=DEBUG, console
...
# The log level for repl.Main remains WARN
log4j.logger.org.apache.spark.repl.Main=WARN{code}
If you launch REPL with the configuration, INFO level logs appear even though
the log level for REPL is WARN.
{code:java}
・・・
19/12/08 23:31:38 INFO Utils: Successfully started service 'sparkDriver' on
port 33083.
19/12/08 23:31:38 INFO SparkEnv: Registering MapOutputTracker
19/12/08 23:31:38 INFO SparkEnv: Registering BlockManagerMaster
19/12/08 23:31:38 INFO BlockManagerMasterEndpoint: Using
org.apache.spark.storage.DefaultTopologyMapper for getting topology information
19/12/08 23:31:38 INFO BlockManagerMasterEndpoint: BlockManagerMasterEndpoint up
19/12/08 23:31:38 INFO SparkEnv: Registering BlockManagerMasterHeartbeat
・・・{code}
Before SPARK-26753 was applied, those INFO level logs are not shown with the
same log4j.properties.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
