Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Tue, 28 Jan 2014 18:41:38 +0000 (UTC)
From: "Anoop Sam John (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12691690.1390934390887.27376.1390934498527@arcas>
In-Reply-To: <JIRA.12691690.1390934390887@arcas>
References: <JIRA.12691690.1390934390887@arcas>
Subject: [jira] [Created] (HBASE-10434) Store Tag compression information
 for a WAL in its header
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Anoop Sam John created HBASE-10434:
--------------------------------------

             Summary: Store Tag compression information for a WAL in its header
                 Key: HBASE-10434
                 URL: https://issues.apache.org/jira/browse/HBASE-10434
             Project: HBase
          Issue Type: Bug
    Affects Versions: 0.98.0
            Reporter: Anoop Sam John
            Assignee: Anoop Sam John
             Fix For: 0.98.0, 0.99.0


We can enable/disable tag compression along with WAL compression using the config,
hbase.regionserver.wal.tags.enablecompression ->  Defaults to true so that compress tags when WAL compress is ON.

We are not storing this info abt whether a WAL containing compressed tags or not in the WAL header and use that in the read path. So dynamic change of this in some servers may cause issue when  an RS having this value as true have to read and split a WAL generated from n RS where this value was false.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)