hbase-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/HBASE-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240012#comment-13240012
] 

Himanshu Vashishtha commented on HBASE-5655:
--------------------------------------------

Yes, it will not roll over the log on a date change.
Disk space is not the only issue for DRFA; its java doc says there are also possible concurrency
issues (or data loss).

"DailyRollingFileAppender has been observed to exhibit synchronization issues and data loss.
The log4j extras companion includes alternatives which should be considered for new deployments
and which are discussed in the documentation for org.apache.log4j.rolling.RollingFileAppender."

Therefore, I think it will be a positive move if we switch to RFA as default; and let users
set an env param in case they do want to use DRFA one. 
Its just an idea, though :)
                
> 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
>
> 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