[
https://issues.apache.org/jira/browse/HBASE-9110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752942#comment-13752942
]
stack commented on HBASE-9110:
------------------------------
Changed my mind. I think we should just commit this and try it as part of the
0.96.0RC0 testing.
Here is some feedback on the patch.
Will this work:
+ executeTool("Namespace upgrade", new NamespaceUpgrade(),
+ new String[] { "--upgrade" }, 0);
+ executeTool("Znode upgrade", new ZKDataMigrator(), null, 0);
+ doOfflineLogSplitting();
Does ns upgrade REMOVE -ROOT-?
Is this right?
doOfflineLogSplitting
It is looking for WALs in the -ROOT- dir it seems? Don't you want to OPEN the
-ROOT- region and read out of it the name of the server that was hosting .META.
and split its logs?
> 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
