phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Palanisamy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5321) Set Log4j Threshold to ALL
Date Fri, 07 Jun 2019 19:33:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858927#comment-16858927
] 

Karthik Palanisamy commented on PHOENIX-5321:
---------------------------------------------

[~rajeshbabu] can you please take a took?

> Set Log4j Threshold to ALL
> --------------------------
>
>                 Key: PHOENIX-5321
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5321
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0
>            Reporter: Karthik Palanisamy
>            Assignee: Karthik Palanisamy
>            Priority: Minor
>         Attachments: PHOENIX-5321.master.v1.patch
>
>
> The problem in enabling debug log with the export command (export PHOENIX_OPTS="-Dpsql.root.logger=DEBUG,console"). Log4j.properties
file has a hardcoded value for log4j.threshold which set to INFO as our default value. So
all log events with lower level than threshold are ignored by the appender (ALL < TRACE
< DEBUG < INFO < WARN < ERROR < FATAL < OFF). for INFO threshold, DEBUG
and TRACE logs are ignored. 
> Log4j.threshold is not required since we pass root logger (-Dpsql.root.logger=INFO,DRFA)
setting during Query server startup (queryserver.py). 
> Log4j.threshold can be removed or set to ALL (default).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message