[
https://issues.apache.org/jira/browse/HBASE-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241883#comment-13241883
]
Himanshu Vashishtha commented on HBASE-5655:
--------------------------------------------
It will be good to know whether these failures are caused by this patch or are
they just flaky.
Looking at the logs for TestTAbleMapReduce's failures, it seems metrics2 were
not loaded, and it gave out NFE:
"attempt_20120329220930011_0001_r_000002_0: 2012-03-29 22:09:50,378 WARN
[main] impl.MetricsSystemImpl(137): Metrics system not started: Cannot locate
configuration: tried hadoop-metrics2-reducetask.properties,
hadoop-metrics2.properties"
Shall I look into it, or are they just flaky. I can't correlate these failures
with log4j rolling policy change as of now.
> 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
> Attachments: 5655-v1.patch, HBase-5655-v2.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
