You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Elliott Clark (JIRA)" <ji...@apache.org> on 2014/12/19 23:58:13 UTC

[jira] [Updated] (HBASE-5238) Add a log4j category for all edits to META/ROOT

     [ https://issues.apache.org/jira/browse/HBASE-5238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliott Clark updated HBASE-5238:
---------------------------------
    Affects Version/s:     (was: 0.94.0)

> 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
>            Reporter: Todd Lipcon
>            Priority: Minor
>              Labels: beginner
>
> 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)