[
https://issues.apache.org/jira/browse/HBASE-5238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381184#comment-14381184
]
Hudson commented on HBASE-5238:
-------------------------------
FAILURE: Integrated in HBase-TRUNK #6304 (See
[https://builds.apache.org/job/HBase-TRUNK/6304/])
HBASE-5238 Add a log4j category for all edits to META/ROOT (andrey.stepachev:
rev e26c4e4e6733ea715fb33e4bd9df9ea2d32d5408)
* hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
* conf/log4j.properties
> 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
> Fix For: 2.0.0
>
> Attachments: HBASE-5238.patch, HBASE-5238.patch, HBASE-5238.v2.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)
