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:21:37 UTC
[jira] [Updated] (SPARK-11354) Expose custom log4j to executor page
in Spark standalone cluster
[ https://issues.apache.org/jira/browse/SPARK-11354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon updated SPARK-11354:
---------------------------------
Labels: bulk-closed (was: )
> Expose custom log4j to executor page in Spark standalone cluster
> -----------------------------------------------------------------
>
> Key: SPARK-11354
> URL: https://issues.apache.org/jira/browse/SPARK-11354
> Project: Spark
> Issue Type: Improvement
> Components: Web UI
> Reporter: Yongjia Wang
> Priority: Minor
> Labels: bulk-closed
> Attachments: custom log4j on executor page.png
>
>
> Spark uses log4j, which is very flexible. However, on the executor page in standalone cluster, only stdout and stderr are shown in the UI. In the default log4j profile, all messages are forwarded to System.err which is, in turn, written to the file stderr in executor directory. Similarly, stdout is written to the stdout file in executor directory.
> It would be very useful to show all the file appenders configured in a custom log4j profile. Right now, these file appenders are written to the executor directory, but they are not exposed to the UI.
--
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