[
https://issues.apache.org/jira/browse/HBASE-25902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354241#comment-17354241
]
Pankaj Kumar commented on HBASE-25902:
--------------------------------------
We faced NoSuchColumnFamilyException while upgrading 1.3.x cluster to HBase
2.2.x.
Steps:
1. Install HBase 2.2.x cluster
2. Stop old HBase 1.3.x cluster
3. Start HBase 2.2.x cluster with existing HDFS & ZK data
Default value of _hbase.migrate.table.state.from.zookeeper_ is true, so during
HMaster startup TableStateManager will try to mirror the table state from ZK to
meta table which will fail because meta table don't have table CF during in old
1.3.x cluster.
So HMaster startup will fail always untill we setÂ
_hbase.migrate.table.state.from.zookeeper_ to false, I have attached snapshot
of the exception trace, kindly refer there.
> 1.x to 2.3.x upgrade does not work; you must install an hbase2 that is
> earlier than hbase-2.3.0 first
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-25902
> URL: https://issues.apache.org/jira/browse/HBASE-25902
> Project: HBase
> Issue Type: Bug
> Components: meta, Operability
> Affects Versions: 2.3.0, 2.4.0
> Reporter: Michael Stack
> Priority: Critical
> Attachments: NoSuchColumnFamilyException.png
>
>
> Making note of this issue in case others run into it. At my place of employ,
> we tried to upgrade a cluster that was an hbase-1.2.x version to an
> hbase-2.3.5 but it failed because meta didn't have the 'table' column family.
> Up to 2.3.0, hbase:meta was hardcoded. HBASE-12035 added the 'table' CF for
> hbase-2.0.0. HBASE-23782 (2.3.0) undid hardcoding of the hbase:meta schema;
> i.e. reading hbase:meta schema from the filesystem. The hbase:meta schema is
> only created on initial install. If an upgrade over existing data, the
> hbase-1 hbase:meta will not be suitable for hbase-2.3.x context as it will be
> missing columnfamilies needed to run (HBASE-23055 made it so hbase:meta could
> be altered (2.3.0) but probably of no use since Master won't come up).
> It would be a nice-to-have if a user could go from hbase1 to hbase.2.3.0 w/o
> having to first install an hbase2 that is earlier than 2.3.0 but needs to be
> demand before we would work on it; meantime, install an intermediate hbase2
> version before going to hbase-2.3.0+ if coming from hbase-1.x
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
