hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Himanshu Vashishtha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9110) Meta region edits not recovered while migrating to 0.96.0
Date Tue, 27 Aug 2013 00:08:51 GMT

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

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

It looks like hbck can help us in situation where meta is not flushed.
On a 0.94.x cluster, I tried migration with some unflushed meta edits (basically, create table
waledits). I killed the meta server before upgrade. 
The edits were not there in meta immediately after migration, but appears correctly after
running "bin/hbase hbck -fixAssignments, -fixMeta".

It definitely needs some more testing.

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

Mime
View raw message