hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Stepachev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5238) Add a log4j category for all edits to META/ROOT
Date Tue, 24 Mar 2015 10:42:52 GMT

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

Andrey Stepachev commented on HBASE-5238:
-----------------------------------------

toJSON prints only column families and datasize. does it makes sense? Seems harmless for me.
(sorry for late answer)

> 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, 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)

Mime
View raw message