spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacek Laskowski (JIRA)" <>
Subject [jira] [Commented] (SPARK-21728) Allow SparkSubmit to use logging
Date Wed, 30 Aug 2017 18:57:01 GMT


Jacek Laskowski commented on SPARK-21728:

The idea behind the custom {{conf/}} is to disable all the logging and enable
only {{org.apache.spark.sql.execution.streaming}} currently.

$ cat conf/

# Set everything to be logged to the console
log4j.rootCategory=OFF, console
log4j.appender.console.layout.ConversionPattern=%d{yy/MM/dd HH:mm:ss} %p %c{1}: %m%n

# Set the default spark-shell log level to WARN. When running the spark-shell, the
# log level for this class is used to overwrite the root logger's log level, so that
# the user can have different defaults for the shell and regular Spark apps.

# Settings to quiet third party logs that are too verbose$exprTyper=INFO$SparkILoopInterpreter=INFO

# SPARK-9183: Settings to avoid annoying messages when looking up nonexistent UDFs in SparkSQL
with Hive support

# Structured Streaming

> Allow SparkSubmit to use logging
> --------------------------------
>                 Key: SPARK-21728
>                 URL:
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 2.3.0
>            Reporter: Marcelo Vanzin
>            Assignee: Marcelo Vanzin
>            Priority: Minor
>             Fix For: 2.3.0
> Currently, code in {{SparkSubmit}} cannot call classes or methods that initialize the
Spark {{Logging}} framework. That is because at that time {{SparkSubmit}} doesn't yet know
which application will run, and logging is initialized differently for certain special applications
(notably, the shells).
> It would be better if either {{SparkSubmit}} did logging initialization earlier based
on the application to be run, or did it in a way that could be overridden later when the app
> Without this, there are currently a few parts of {{SparkSubmit}} that duplicates code
from other parts of Spark just to avoid logging. For example:
> * [downloadFiles|]
replicates code from Utils.scala
> * [createTempDir|]
replicates code from Utils.scala and installs its own shutdown hook
> * a few parts of the code could use {{SparkConf}} but can't right now because of the
logging issue.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message