[
https://issues.apache.org/jira/browse/AMBARI-17886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396186#comment-15396186
]
Hudson commented on AMBARI-17886:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #5400 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5400/])
AMBARI-17886 : Disable INFO logs from HadoopMetrics2Reporter for hive
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=55b95822476a0211feb06740b35ba13e0da37d8a])
*
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-log4j.xml
*
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-log4j2.xml
*
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-log4j.xml
> Disable INFO logs from HadoopMetrics2Reporter for hive
> ------------------------------------------------------
>
> Key: AMBARI-17886
> URL: https://issues.apache.org/jira/browse/AMBARI-17886
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17886-2.patch, AMBARI-17886-4.patch
>
>
> Out of disk space issues are seen due to the sheer amount of logs being
> produced by hive after addition of metrics. For this, a single change needs
> to be done to the log4j properties offered by Ambari to fix this.
> In Hive Config -> "Advanced hive-log4j", the following needs to be added.
> {noformat}
> # Silence HadoopMetrics2Reporter INFO logs
> log4j.logger.com.github.joshelser.dropwizard.metrics.hadoop=WARN,DRFA
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
