Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Tue, 22 Jan 2013 22:56:12 +0000 (UTC)
From: "Elliott Clark (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12628815.1358895286552.175818.1358895372993@arcas>
In-Reply-To: <JIRA.12628815.1358895286552@arcas>
References: <JIRA.12628815.1358895286552@arcas>
Subject: [jira] [Created] (HBASE-7647) 0.94 hfiles v2.1 are not backwards
 compatible with HFilev2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Elliott Clark created HBASE-7647:
------------------------------------

             Summary: 0.94 hfiles v2.1 are not backwards compatible with HFilev2.0
                 Key: HBASE-7647
                 URL: https://issues.apache.org/jira/browse/HBASE-7647
             Project: HBase
          Issue Type: Bug
          Components: HFile
    Affects Versions: 0.94.4
            Reporter: Elliott Clark
            Assignee: Elliott Clark


When doing a rolling re-start from 0.92.x to 0.94.x any hfiles written by 0.94 are incompatibile with any of the 0.92 region servers.  This is caused by the checksums being put into 0.94.

* a minor version was added
* checksums were put into the block
* checksum meta data was added to block headers.

I propose that since these changes are only needed if using hbase.regionserver.checksum.verify, they should be turned off if that option is turned off.  Doing so will allow rolling upgrades to go smoother.

If a user wants to go from a 0.92 cluster to a 0.94 cluster with hbase.regionserver.checksum.verify they can:
* Roll out 0.94
* Change hbase-site.xml
* roll restart the region servers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira