[
https://issues.apache.org/jira/browse/HBASE-9110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-9110:
-------------------------
Release Note: Adds a step to migration where we split any outstanding WAL
files. This process is not distributed so will be slower than the distributed
version that runs on cluster startup so, make sure there are few WALs to split
at this step by making sure the cluster shutdown is clean pre-upgrade.
> 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
> Assignee: Himanshu Vashishtha
> Priority: Critical
> Fix For: 0.98.0, 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
