Known Issues

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

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.
With default replication configurations, small files consuming more time to complete the replication process
You can increase the number of mappers to improve the replication performance.
Hive replication policy fails when a table is dropped in the source database (export tables) when the replication job is running.
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.
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.
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.
Replication policies with an empty name do not appear on the Replication Policies page.
Provide a unique replication policy name during replication policy creation.
A NullPointerException appears when you delete an HBase replication policy for which the policy creation failed because a table in the policy did not exist on the source cluster.
After the failed delete action (using the Actions > Delete option on the Replication Policies page), select Actions > Force Delete to get the policy deleted.
If the snapshot export/import fails during HBase replication policy creation, and then you choose the Actions > Retry Failed Snapshots option for the replication policy on the Replication Policies page, the HBase peer is not enabled even if there were no export/import failures during the retry action. In this scenario, the replication peer in the HBase service remains disabled and the Retry Failed Snapshots action fails.
Delete the replication policy and re-create it.
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 action.
In CDH 5 clusters, create a ‘test’ HBase replication policy with a small table. This creates the HBase peer.