Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 20 Feb 2015 12:13:12 +0000 (UTC)
From: "Andrey Stepachev (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12539183.1327082069000.94406.1424434392152@Atlassian.JIRA>
In-Reply-To: <JIRA.12539183.1327082069000@Atlassian.JIRA>
References: <JIRA.12539183.1327082069000@Atlassian.JIRA>
 <JIRA.12539183.1327082069715@arcas>
Subject: [jira] [Updated] (HBASE-5238) Add a log4j category for all edits to
 META/ROOT
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrey Stepachev updated HBASE-5238:
------------------------------------
             Assignee: Andrey Stepachev
    Affects Version/s: 2.0.0
               Status: Patch Available  (was: Open)

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