Troubleshooting replication policies in CDP Public Cloud
The troubleshooting scenarios in this topic help you to troubleshoot issues in the Replication Manager service in CDP Public Cloud.
What are different methods to identify errors while troubleshooting a failed replication policy?
Remedy
HDFS replication policies fail when the export HTTPS_PROXY environment variable is set to access AWS through proxy servers
Remedy
Cannot find destination clusters when you ping using their host names
Condition
The source cluster hosts for HBase replication policies do not find the destination clusters when you ping by their host names.
Cause
This might occur for on-premises clusters such as CDP Private Cloud Base clusters or CDH clusters because the source clusters are not on the same network as the destination Data Hub. Therefore, hostnames cannot be resolved by the DNS service on the source cluster.
Remedy
10.115.74.181 dx-7548-worker2.dx-hbas.x2-8y.dev.dr.work
10.115.72.28 dx-7548-worker1.dx-hbas.x2-8y.dev.dr.work
10.115.73.231 dx-7548-worker0.dx-hbas.x2-8y.dev.dr.work
10.115.72.20 dx-7548-master1.dx-hbas.x2-8y.dev.dr.work
10.115.74.156 dx-7548-master0.dx-hbas.x2-8y.dev.dr.work
10.115.72.70 dx-7548-leader0.dx-hbas.x2-8y.dev.dr.work
HBase replication policy fails when Perform Initial Snapshot is chosen
Condition
An HBase replication policy fails for COD on Microsoft Azure when the Perform Initial Snapshot option is chosen but data replication is successful when the option is not chosen.
Cause
This issue appears when the required managed identity of source roles are not assigned.