Cloudera Operational Database migration

You can migrate HBase and Phoenix tables from CDH or HDP to Cloudera Operational Database Cloudera on cloud where the Store File Tracking (SFT) is enabled.

When you are migrating from CDH or HDP to an SFT enabled Cloudera Operational Database Cloudera on cloud, ensure that you create an SFT enabled Cloudera Operational Database database on the target cluster. For more details on creating a Cloudera Operational Database database, see Store File Tracking usage.

To migrate from CDH or HDP to an SFT enabled Cloudera Operational Database Cloudera on cloud, see HBase Migration through Cloudera Replication Manager.

Even after restoring the snapshots on the SFT enabled Cloudera Operational Database Cloudera on cloud, the resulting tables do not load the correct SFT configurations automatically; SFT considers the DEFAULT tracker, which still relies on the temporary directories and renames.

You must convert the DEFAULT tracker to the FILE tracker in each of the restored table configurations by defining the MIGRATION tracker at the table level configurations. Consider the following example to switch the tracker from DEFAULT to FILE in a table configuration.

alter 'my-table', CONFIGURATION => {'hbase.store.file-tracker.impl' => 'MIGRATION',
'hbase.store.file-tracker.migration.src.impl' => 'DEFAULT',
'hbase.store.file-tracker.migration.dst.impl' => 'FILE'}

Once all table regions are online, disable the MIGRATION by setting hbase.store.file-tracker.migration.dst.impl value as hbase.store.file-tracker.impl. In the above example, this can be represented as.

alter 'my-table', CONFIGURATION => {'hbase.store.file-tracker.impl' => 'FILE'}