[
https://issues.apache.org/jira/browse/HBASE-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239578#comment-13239578
]
Himanshu Vashishtha commented on HBASE-5655:
--------------------------------------------
It involves adding a new appender description in log4j.properties file, and
making the hbase-daemon.sh to set the root logger after reading from env rather
than hard coding.
More specifically, in hbase-daemon.sh:
using export HBASE_ROOT_LOGGER=${HBASE_ROOT_LOGGER:-"INFO,RFA"}, in place of
export HBASE_ROOT_LOGGER="INFO,DRFA"
I have done the changes and tested on my local. Please share your thoughts.
> 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
>
>
> 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
