Xiangrui Meng created SPARK-3357:
------------------------------------
Summary: Internal log messages should be set at DEBUG level
instead of INFO
Key: SPARK-3357
URL: https://issues.apache.org/jira/browse/SPARK-3357
Project: Spark
Issue Type: Improvement
Components: Spark Core
Affects Versions: 1.1.0
Reporter: Xiangrui Meng
Assignee: Xiangrui Meng
Priority: Minor
spark-shell shows INFO by default, so we should carefully choose what to show
at INFO level. For example, if I run
{code}
sc.parallelize(0 until 100).count()
{code}
and wait for one minute or so. I will see messages that mixed with the current
input box, which is annoying:
{code}
scala> 14/09/02 17:09:00 INFO BlockManager: Removing broadcast 0
14/09/02 17:09:00 INFO BlockManager: Removing block broadcast_0
14/09/02 17:09:00 INFO MemoryStore: Block broadcast_0 of size 1088 dropped from
memory (free 278019440)
14/09/02 17:09:00 INFO ContextCleaner: Cleaned broadcast 0
{code}
Does a user need to know when a broadcast variable is removed? Maybe not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
