You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:35:44 UTC

[jira] [Resolved] (SPARK-13006) Use Log4j for Spark Standalone Executor Logging

     [ https://issues.apache.org/jira/browse/SPARK-13006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyukjin Kwon resolved SPARK-13006.
----------------------------------
    Resolution: Incomplete

> Use Log4j for Spark Standalone Executor Logging
> -----------------------------------------------
>
>                 Key: SPARK-13006
>                 URL: https://issues.apache.org/jira/browse/SPARK-13006
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>            Reporter: Alan Braithwaite
>            Priority: Major
>              Labels: bulk-closed, executors, logging
>
> Currently it logs to scratch space which is shared with things like the application jar.  It makes it very difficult to collect these logs effectively and cleanly.
> https://github.com/apache/spark/blob/08c781ca672820be9ba32838bbe40d2643c4bde4/core/src/main/scala/org/apache/spark/deploy/worker/ExecutorRunner.scala#L166-L172



--
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