Ya i think that is the property that controls the archiving of the logs. So the other properties are wrt Log Rolling and no of logs that is needed before rolling happens. But these parameters determine the time taken for recovery in case of RS failure.
Your purpose is to maintain the logs so that they dont get deleted? IF you are using 0.94 version then you have a way to plugin your own logcleaner class. 'BaseLogCleanerDelegate' is the default thing available. Customise your logcleaner as per your requirement so that you can have a back up of the logs. Hope this helps. Regards Ram On Sat, Feb 2, 2013 at 3:39 PM, yonghu <yongyong...@gmail.com> wrote: > Dear Ram, > > Thanks for your response. > > Yes Log means WAL logs. Now, I can define a postWALWrite trigger to > write the WAL entries into the specific file as I want, however, it's > too slow. The problem is that hbase automatically delete log entries. > However, I found some properties such as hbase.master.logcleaner.ttl > which I can use to indicate how long logs can exist. I think it can > control the life cycle of the logs. If you know other opions, please > let me know. > > Thanks! > > Yong > > On Sat, Feb 2, 2013 at 10:30 AM, ramkrishna vasudevan > <ramkrishna.s.vasude...@gmail.com> wrote: > > Logs of hbase you mean the normal logging or the WAL logs. Sorry am not > > getting your question here. > > WAL trigger is for the WAL logs. > > > > Regards > > Ram > > > > On Sat, Feb 2, 2013 at 1:31 PM, yonghu <yongyong...@gmail.com> wrote: > > > >> Hello, > >> > >> For some reasons, I need to analyze the log of hbase. However, the log > >> will be automatically deleted by GC of JVM (if I understand right). I > >> wonder if there is a way to close automatically log deletion in HBase. > >> By the way, I can collect Log by WAL trigger, but it's really slow. > >> > >> regards! > >> > >> Yong > >> >
