Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 20 Nov 2012 14:46:58 +0000 (UTC)
From: "Oleg Zhurakousky (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <394096095.6902.1353422819005.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-7191) HBCK - Add offline create/fix
 hbase.version and hbase.id
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501214#comment-13501214 ] 

Oleg Zhurakousky commented on HBASE-7191:
-----------------------------------------

Actually, this affects other versions as well
{code}
HBase 0.94.1
{code}
Further more; FSUtils spits out a misleading message
{code}
 String msg = "File system needs to be upgraded."
      + "  You have version " + version
      + " and I want version " + HConstants.FILE_SYSTEM_VERSION
      + ".  Run the '${HBASE_HOME}/bin/hbase migrate' script.";
{code}
As far as I can tell 'migrate' script is no longer available

One would think 'hbase hbck -fixVersionFile' would do the trick, but that requires a running instance of HBase which we can't start unless those two files are in tact 

The current workaround is to temporarily change the value of 'hbase.rootdir' -> start/stop hbase (this will re-create the two files) -> copy those files to the original 'hbase.rootdir' and change 'hbase.rootdir' to point back to the original one. However, this is obviously a hack. May what really needs to happen is to have and offline option of 'hbase hbck -fixVersionFile'.

                
> HBCK - Add offline create/fix hbase.version and hbase.id 
> ---------------------------------------------------------
>
>                 Key: HBASE-7191
>                 URL: https://issues.apache.org/jira/browse/HBASE-7191
>             Project: HBase
>          Issue Type: Improvement
>          Components: hbck
>    Affects Versions: 0.96.0
>            Reporter: Enis Soztutar
>
> One of our clients run into a problem, in which they have the hbase.root.dir, and cluster data, but their hbase.id and hbase.version files are corrupted. HMaster creates those on start, but not if there is already existing data.
> We can add smt like --fixIdFile, and ability for HBCK to do some offline repairs for the version file. 

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