[
https://issues.apache.org/jira/browse/HBASE-28376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819046#comment-17819046
]
Duo Zhang commented on HBASE-28376:
-----------------------------------
I think this is partly because of HBASE-23055, where we change the hard coded
meta table descriptor so we can alter meta table to change some configs.
Before HBASE-23055. the meta table will have the ns family automatically after
upgrading, but now, we need an alter table operation to add a family.
Let me think how to do this.
Thanks.
> Column family ns does not exist in region during upgrade to 3.0.0-beta-2
> ------------------------------------------------------------------------
>
> Key: HBASE-28376
> URL: https://issues.apache.org/jira/browse/HBASE-28376
> Project: HBase
> Issue Type: Bug
> Components: meta
> Affects Versions: 3.0.0-beta-1
> Reporter: Bryan Beaudreault
> Assignee: Duo Zhang
> Priority: Blocker
>
> Upgrading from 2.5.x to 3.0.0-alpha-2, migrateNamespaceTable kicks in to copy
> data from the namespace table to an "ns" family of the meta table. If you
> don't have an "ns" family, the migration fails and the hmaster will crash
> loop. You then can't rollback, because the briefly alive upgraded hmaster
> created a procedure that can't be deserialized by 2.x (I don't have this log
> handy unfortunately). I tried pushing code to create the ns family on
> startup, but it doesnt work becuase the migration happens while the hmaster
> is still initializing.
> So it seems imperative that you create the ns family before upgrading. We
> should handle this more gracefully.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
