You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2024/03/10 08:47:00 UTC

[jira] [Resolved] (HBASE-28376) Column family ns does not exist in region during upgrade to 3.0.0-beta-2

     [ https://issues.apache.org/jira/browse/HBASE-28376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang resolved HBASE-28376.
-------------------------------
    Hadoop Flags: Reviewed
      Resolution: Fixed

Pushed to master and branch-3.

Thanks [~bbeaudreault] for reviewing!

> 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
>              Labels: pull-request-available
>             Fix For: 3.0.0-beta-2
>
>
> 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)