Resolve execution failures when Cloudera Replication Manager policy creation
returns HTTP 400 or 409 errors.
Symptom: An execution step fails with
Failed to create replication policy or HTTP 400/409 from Cloudera Replication Manager.
For Cloudera Replication Manager setup and integration, see Cloudera Replication Manager Integration.
-
Verify that Cloudera Replication Manager is running on the target cluster
Cloudera Manager host.
-
If the policy name already exists, delete the existing policy through the Cloudera Manager API and retry.
See Database and Data Cleanup for listing and deleting replication
policies.
-
Ensure the source cluster is registered as a peer in the target cluster's Cloudera Replication Manager configuration.
-
Verify that source paths in the migration plan exist on the source cluster.
