You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Thincrs (JIRA)" <ji...@apache.org> on 2018/12/04 22:33:00 UTC
[jira] [Commented] (SPARK-26235) Change log level for
ClassNotFoundException/NoClassDefFoundError in SparkSubmit to Error
[ https://issues.apache.org/jira/browse/SPARK-26235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709357#comment-16709357 ]
Thincrs commented on SPARK-26235:
---------------------------------
A user of thincrs has selected this issue. Deadline: Tue, Dec 11, 2018 10:32 PM
> Change log level for ClassNotFoundException/NoClassDefFoundError in SparkSubmit to Error
> ----------------------------------------------------------------------------------------
>
> Key: SPARK-26235
> URL: https://issues.apache.org/jira/browse/SPARK-26235
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 3.0.0
> Reporter: Gengliang Wang
> Assignee: Gengliang Wang
> Priority: Trivial
> Fix For: 3.0.0
>
>
> In my local setup, I set log4j root category as ERROR (https://stackoverflow.com/questions/27781187/how-to-stop-info-messages-displaying-on-spark-console , first item show up if we google search "set spark log level".)
> When I run such command
> ```
> spark-submit --class foo bar.jar
> ```
> Nothing shows up, and the script exits.
> After quick investigation, I think the log level for ClassNotFoundException/NoClassDefFoundError in SparkSubmit should be ERROR instead of WARN.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org