Known Issues

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

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.
When the first HBase replication policy is created between two clusters where the source cluster is an on-premises cluster, sometimes the policy's status shows Waiting for 'Continue Setup' action call for the first few seconds.
No user action is required. The status automatically is updated to Configuring clusters after a few seconds.
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.
Replication Manager runs the clone_snasphot command when restoring snapshots on SFT-enabled clusters without setting the SFT attributes on the table.

To resolve this issue, run the steps mentioned in COD migration topic on the replicated tables in the target database after the HBase replication policy has been created.

When you delete an HBase replication policy, the HBase peer used in the policy is also deleted if a replicated table name has the - character. Note that the HBase peer is deleted even when there are existing HBase replication policies using this peer. This issue also occurs if a replicated table in any of the policies that uses this peer has the - character in its name.
Replication policies with an empty name do not appear on the Replication Policies page.
Provide a unique replication policy name during replication policy creation.