Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 25 Jul 2016 20:27:20 +0000 (UTC)
From: "Aravindan Vijayan (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12992326.1469464375000.127140.1469478440735@Atlassian.JIRA>
In-Reply-To: <JIRA.12992326.1469464375000@Atlassian.JIRA>
References: <JIRA.12992326.1469464375000@Atlassian.JIRA> <JIRA.12992326.1469464375610@arcas>
Subject: [jira] [Updated] (AMBARI-17886) Disable INFO logs from
 HadoopMetrics2Reporter for hive
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 25 Jul 2016 20:27:22 -0000


     [ https://issues.apache.org/jira/browse/AMBARI-17886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aravindan Vijayan updated AMBARI-17886:
---------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> 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: Blocker
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17886-2.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)