Cloudera Docs

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
HBase replication policies do not support source or destination CDP Public Cloud clusters created using the 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.
OPSAPS-70282
You cannot create HBase replication policies if the target Cloudera Manager > Clusters > HBase service > Configuration > HBase ZooKeeper Secure Client Enabled property is enabled.
Disable the HBase ZooKeeper Secure Client Enabled property, and then create HBase replication policies.
OPSAPS-71317, OPSAPS-71318
When you delete an HBase replication policy, its peer is not removed if a table name in the replication policy contains a period. This issue is observed when the source Cloudera Manager is 7.4.4, 7.6.1, 7.6.7, 7.7.1, 7.7.3 CHFx, or CDP Public Cloud 7.2.16 using source Cloudera Manager 7.9.2, or CDP Public Cloud 7.2.17 using source Cloudera Manager 7.11.0, and unsupported target Cloudera Manager versions.
To resolve the issue:
  • Upgrade to a supported target Cloudera Manager.
  • Upgrade the source Cloudera Manager to 7.11.3 CHFx or higher.
  • Remove the period from the table name on the source cluster.
  • Perform the following steps to remove the peer associated with the deleted replication policy manually:
    1. Confirm that the HBase peer in the source HBase cluster does not contain any tables. If there are any tables, this indicates that there might be other HBase replication policies between these clusters. In such instances, you can contact your Cloudera account team.
    2. Manually remove the peer using the remove_peer [***PEER ID***] HBase command.
    3. Create an HBase replication policy in Replication Manager.
DMX-3888
The existing Hive replication policies do not appear on the Replication Policies page after you upgrade the target cluster from CDP Public Cloud 7.2.16 using Cloudera Manager 7.9.0 to CDP Public Cloud 7.2.17 using Cloudera Manager 7.11.0-h2. This issue appears if the existing replication policies were created using external APIs and the API payload included the rangerImportProperties and sentryExportProperties attributes.
Before you upgrade the target cluster, verify whether the HIVE_REPLICATION_SENTRY_EXPORT_PROPERTIES feature flag is enabled. If the feature flag is not enabled, you must remove the rangerImportProperties and sentryExportProperties attributes from the existing Hive replication policies, and then upgrade the target cluster.