Known Issues

This section lists known issues that you might run into while using the Replication Manager service.

DOCS-13504

When you create an HBase replication policy between a source cluster using Cloudera Manager version is 7.6.0-patch5366 or higher and a target cluster using Cloudera Manager version is 7.6.0 or lower, the first-time setup is not initiated and the following misleading message appears during policy creation:

Skipping Replication Setup because it has already been done.

To resolve this issue, upgrade the target cluster to Cloudera Manager version to 7.6.0-patch5366 or higher.

DMX-518

Hive replication policy fails when a table is dropped in the source database (export tables) when the replication job is running.

DMX-519

If snapshots on the /user/hive/warehouse directory is not enabled, Hive replication policy fails when inserts are done on a source table during replication job run.

DMX-521

While running Hive replication policy, if you drop a table, it is not dropped on the target cluster. The data still remains and 'show tables' displays the dropped table after successful replication instances.

DMX-1455

An HBase replication policy from Cloudera Operational Database COD to COD cluster fails if you select the Perform Initial Snapshot option in the Create Replication Policy wizard, and the source and destination COD clusters use different AWS accounts.

DMX-2923

When you create an HBase replication policy with the Perform Initial Snapshot option in a bi-directional replication setup from the disaster recovery cluster to the production cluster, the original table gets dropped and it is recreated with the content in the disaster recovery cluster. Therefore, the original content of the table is lost.

When you create the HBase replication policy in a bi-directional replication setup from the disaster recovery cluster to the production cluster, do not select the Perform Initial Snapshot option.

OPSAPS-66327

The HBase peer can be created in the disabled state in CDH 6.0 or higher clusters. However, HBase peer cannot be created in disabled state in CDH 5 clusters and the peer remains enabled throughout the replication setup process. As a workaround, you can create a ‘test’ HBase replication policy with a small table in CDH 5 clusters. This creates the HBase peer.

OPSAPS-69210

The Failed to copy HDFS file to remote HDFS error appears during the HBase replication policy creation process if the CDP Public Cloud cluster destination cluster was created using Micro Duty template.

OPSAPS-69782

HBase replication using HBase replication policies between two Data Hubs/COD clusters fail if all the following conditions are true:

• The destination Data Hub/COD cluster’s Cloudera Manager version is 7.9.0-h7 through 7.9.0-h9 or 7.11.0-h2 through 7.11.0-h4, or 7.12.0.0.
• The source Data Hub/COD cluster's Cloudera Manager major version is higher than the destination cluster's Cloudera Manager major version.
• The Initial Snapshot option is chosen during the HBase replication policy creation process and/or the source cluster is already participating in another HBase replication setup as a source or destination with a third cluster.

Upgrade the destination cluster's Cloudera Manager to a major version that is equal to or greater than the source cluster's Cloudera Manager major version.

OPSAPS-62230

HBase replication command steps for an HBase replication policy might fail if you have configured an automatic delete of /tmp folder content on the destination cluster’s Cloudera Manager server node.