[
https://issues.apache.org/jira/browse/HBASE-28376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825104#comment-17825104
]
Hudson commented on HBASE-28376:
--------------------------------
Results for branch branch-3
[build #164 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/164/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/164/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/164/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/164/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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)
