If log grows so fast that disk space is to be exhausted, verbosity should be lowered.
Do you turn on DEBUG logging ? Cheers On Mar 18, 2014, at 6:08 AM, haosdent <haosd...@gmail.com> wrote: > Thanks for your reply. DailyRollingFileAppender and a cron job could works > in normal scenario. But sometimes log grow too fast, or disk space may use > by other applications. Is there a way make Log more "smart" and choose > policy according to current disk space? > > > On Tue, Mar 18, 2014 at 8:49 PM, Ted Yu <yuzhih...@gmail.com> wrote: > >> Can you utilize >> http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/DailyRollingFileAppender.html? >> >> And have a cron job cleanup old logs ? >> >> Cheers >> >> On Mar 18, 2014, at 5:29 AM, haosdent <haosd...@gmail.com> wrote: >> >>> Sometimes the call of Log.xxx couldn't return if the disk partition of >> Log >>> path is full. And HBase would hang because of this. So I think if there >> is >>> a better way to handle too much log. For example, through a configuration >>> item in hbase-site.xml, we could delete the old logs periodically or >> delete >>> old logs when this disk didn't have enough space. >>> >>> I think HBase hang when disk space isn't enough is unacceptable. Looking >>> forward your ideas. Thanks in advance. >>> >>> -- >>> Best Regards, >>> Haosdent Huang > > > > -- > Best Regards, > Haosdent Huang
