Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 31 Mar 2012 01:39:27 +0000 (UTC)
From: "Zhihong Yu (Updated) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <830315723.41183.1333157967468.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1770831071.23784.1332863668452.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HBASE-5655) Cap space usage of default log4j
 rolling policy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Zhihong Yu updated HBASE-5655:
------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)
    
> Cap space usage of default log4j rolling policy
> -----------------------------------------------
>
>                 Key: HBASE-5655
>                 URL: https://issues.apache.org/jira/browse/HBASE-5655
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.92.1
>            Reporter: Himanshu Vashishtha
>            Assignee: Himanshu Vashishtha
>             Fix For: 0.96.0
>
>         Attachments: 5655-v1.patch, HBase-5655-v2.patch, HBase-5655-v3.patch
>
>
> The current default log4j policy is to use Daily Rolling File Appender (DRFA). At times, its good to have a cap on the maximum size of the logs in order to limit its disk usage. Here is a proposal to set a new file appemder (RFA) as the default appender. It can be configured via env so that existing tools can use the current behavior of using DRFA instead. 
> This is in parallel with jira Hadoop-8149.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira