Manage and monitor Iceberg replication policies

After you create an Iceberg replication policy in , you can perform and monitor various tasks related to the replication policy.

The Replication Policies page displays all the available replication policies, including the Policy Name, Service Type of the policy, Source cluster name, Target cluster name, job Status, and job run history. When you click a policy name, a detailed job run history and an option to modify the replication policy configuration are displayed.

On the Actions menu, you can perform the following tasks on the replication policy:

Option Description
Edit Change the replication policy options as required for non-expired policies that are in active or suspended state. Based on the schedule you choose, the replication policy replicates data.
You can edit the replication policies to better align with changing requirements. For example, you might want to change the frequency of a policy depending on the data size and importance of the data being replicated.

Optionally, expand a replication policy on the Replication Policies page to edit the replication policy options, including frequency (start time cannot be modified if the policy has already started), queue name, maximum bandwidth, and maximum map slots.

Rerun Initiates the replication policy run immediately.
Delete Deletes the replication policy permanently.
View Command Details Opens the latest Iceberg replication policy job page. The steps and substeps display in a tree view. The failed steps are expanded by default, displaying the last 15 lines of the log.

You can also view the command details for a Hive replication policy on the Overview > Issues & Updates panel.

To view the complete log for all the jobs, go to the target cluster Cloudera Manager > Running Commands page.

Collect diagnostic bundle Generates a diagnostic bundle for the replication policy. You can download the bundle as a ZIP file to your machine.

Ensure that you are logged into the instances for both the source and target clusters before you download the bundle in Replication Manager.