[ https://issues.apache.org/jira/browse/HBASE-5238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14330001#comment-14330001 ]
stack commented on HBASE-5238: ------------------------------ Thanks for the log. I don't think I need this 'META: ' prefix you have on all the logging since it all has MetaTableAccessor as class and its all JSON? I can fix on commit. The release not can be improved in that you should say how to 'enable' this extra logging (or rather, I suppose, it looks like it is ON always -- that is so [~octo47]? If so, I see no harm starting there in 1.1.0 and 2.0.0). Thanks. > Add a log4j category for all edits to META/ROOT > ----------------------------------------------- > > Key: HBASE-5238 > URL: https://issues.apache.org/jira/browse/HBASE-5238 > Project: HBase > Issue Type: New Feature > Components: regionserver > Affects Versions: 2.0.0 > Reporter: Todd Lipcon > Assignee: Andrey Stepachev > Priority: Minor > Labels: beginner > Attachments: HBASE-5238.patch, meta2.log > > > Occasionally we run into bugs that have corrected META and written some bad > data to META/ROOT but it's difficult to understand the order in which things > happened. One option is to dump the HLog contents from the servers that > hosted META at that time, but then it's interspersed with all other data. It > would be nice to add a Log4j Logger to which we log all edits being applied > to META and ROOT in textual form at DEBUG level. Then it would be easier to > do a cluster-wide log grep to see what happened when. -- This message was sent by Atlassian JIRA (v6.3.4#6332)