hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Himanshu Vashishtha (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5655) Cap space usage of default log4j rolling policy
Date Fri, 30 Mar 2012 16:52:29 GMT

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

Himanshu Vashishtha updated HBASE-5655:
---------------------------------------

    Release Note: 
This changes the default log rolling scheme from DRFA to RFA. The former rolls over the log
on a date change trigger, while the later rolls over when the log file size reaches a predefined
limit. The issue with DRFA is that it doesn't have the ability to cap the space usage, so
users who are not using host-level log rotation might fill up their log partitions. This results
in a cluster crash. RFA puts a size limit on the log size and therefore is a safer option
in such scenarios. The default file size is 256MB with 20 files (total of 5GB logs). In case
one needs to revert to the original DRFA (for some legacy tools etc), one can set a env variable
HBASE_ROOT_LOGGER to <ROOT_LOGGER_LEVEL,DRFA>. Please refer to the hbase-env.sh for
more details.

    
> 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

        

Mime
View raw message