Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 25 Mar 2015 17:02:53 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12539183.1327082069000.25163.1427302973943@Atlassian.JIRA>
In-Reply-To: <JIRA.12539183.1327082069000@Atlassian.JIRA>
References: <JIRA.12539183.1327082069000@Atlassian.JIRA>
 <JIRA.12539183.1327082069715@arcas>
Subject: [jira] [Commented] (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:comment-tabpanel&focusedCommentId=14380240#comment-14380240 ] 

Andrew Purtell commented on HBASE-5238:
---------------------------------------

META has a fixed system defined schema so I think in this case we don't care if column families are printed.

Keys can definitely be sensitive, we should avoid logging those. One can argue that META is already world readable but a persisted log can leak and the information inside can be read independently of access routes to the cluster. For example, the cluster might be firewalled to prevent random access to META, because keys are sensitive, but here we've slipped them into the log, those log lines are now up in Splunk or Elasticsearch, and network ACLs grant wider access to those.

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