Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 29 Aug 2013 04:28:52 +0000 (UTC)
From: "Himanshu Vashishtha (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12661156.1375373146250.52187.1377750532019@arcas>
In-Reply-To: <JIRA.12661156.1375373146250@arcas>
References: <JIRA.12661156.1375373146250@arcas>
Subject: [jira] [Commented] (HBASE-9110) Meta region edits not recovered
 while migrating to 0.96.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Himanshu Vashishtha commented on HBASE-9110:
--------------------------------------------

Yes, the second patch i uploaded  today has the log splitter logic.
I think we can have it for the RC (i tested it on my local).

(Sent from phone)


> Meta region edits not recovered while migrating to 0.96.0
> ---------------------------------------------------------
>
>                 Key: HBASE-9110
>                 URL: https://issues.apache.org/jira/browse/HBASE-9110
>             Project: HBase
>          Issue Type: Sub-task
>          Components: migration
>    Affects Versions: 0.95.2, 0.94.10
>            Reporter: Himanshu Vashishtha
>            Priority: Critical
>             Fix For: 0.96.0
>
>         Attachments: HBase-9110-v0.patch, HBase-9110-v1.patch
>
>
> I was doing the migration testing from 0.94.11-snapshot to 0.95.0, and faced this issue.
> 1) Do some edits in meta table (for eg, create a table).
> 2) Kill the cluster.
> (I used kill because we would be doing log splitting when upgrading anyway).
> 3) There is some dependency on WALs. Upgrade the bits to 0.95.2-snapshot. Start the cluster.
> Every thing comes up. I see log splitting happening as expected. But, the WAL-data for meta table is missing.
> I could see recovered.edits file for meta created, and placed at the right location. It is just that the new HMaster code tries to recover meta by looking at meta prefix in the log name, and if it didn't find one, just opens the meta region. So, the recovered.edits file, created afterwards, is not honored.
> Opening this jira to let folks give their opinions about how to tackle this migration issue.

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