You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Eli Treuherz (JIRA)" <ji...@apache.org> on 2019/07/08 08:34:00 UTC
[jira] [Created] (LIVY-605) Provide default Log4j initialization
Eli Treuherz created LIVY-605:
---------------------------------
Summary: Provide default Log4j initialization
Key: LIVY-605
URL: https://issues.apache.org/jira/browse/LIVY-605
Project: Livy
Issue Type: Improvement
Components: Core, Server
Affects Versions: 0.6.0
Reporter: Eli Treuherz
Presently, as far as I can tell, a new user must duplicate the log4j.properties.template file into log4j.properties in the conf dir for Livy to run, otherwise it writes
{code:java}
log4j:WARN No appenders could be found for logger (org.apache.livy.server.AccessManager).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
{code}
to the log file and nothing else.
It would be better to bundle the server, or the livy core, with a default log4j file that is initialised if no other one is present, [the same way Spark does|https://github.com/apache/spark/blob/25b97a41ceede7b99a5f835077de94b38743203a/core/src/main/scala/org/apache/spark/internal/Logging.scala#L119]. This would make setting up Livy for the first time that bit more frictionless.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)