[
https://issues.apache.org/jira/browse/HIVE-11751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736340#comment-14736340
]
Prasanth Jayachandran commented on HIVE-11751:
----------------------------------------------
Following is the issue
There is no equivalent of log4j.threshold in log4j2. HIVE-11304 added the value
hive.log.threshold to root logger's level. The appender inside the root logger
has its own level set to the value of hive.log.level. So if hive.log.threshold
is set to ALL then root logger will allow all logging levels but the appender
referenced inside root logger will use hive.log.level (say INFO). As a result,
all loggers evaluate DEBUG/TRACE/INFO expression but later will be filtered by
the appender. The call trace should trace log in ProtobufRpcEngine being
evaluated but then filtered later by the appender. The fix for this issue is to
set hive.log.level to root logger instead of the appender referenced inside.
> hive-exec-log4j2.xml settings causes DEBUG messages to be generated and
> ignored
> -------------------------------------------------------------------------------
>
> Key: HIVE-11751
> URL: https://issues.apache.org/jira/browse/HIVE-11751
> Project: Hive
> Issue Type: Bug
> Reporter: Rajesh Balamohan
> Assignee: Prasanth Jayachandran
> Attachments: hive-exec-log4j2.xml, hive-log4j2.xml,
> hiveserver2_log4j.png
>
>
> Setting "<Property name="hive.log.threshold">INFO</Property>" in
> dist/hive/conf/hive-exec-log4j2.xml fixes the problem. Should it be made as
> default in hive-exec-log4j2.xml? "--hiveconf hive.log.level=INFO" from
> commandline does not have any impact.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)