Managing HBase replication policy

After you create an HBase replication policy in CDP Public Cloud Replication Manager, you can perform and monitor various tasks related to the replication policy. You can also view the job progress and replication logs.

When you click an HBase replication policy on the Replication Policies page, you can perform the following actions and tasks on the replication policy and its jobs:
  • Edit the policy name; view the source cluster name and tables selected in it to be replicated; and view the destination Data Hub or COD and the tables that have been replicated.
  • On the Job History panel, you can view the previous replication jobs, current running job, and one future scheduled job for the replication policy.
    You can also track the following details about each job:
    • Type of job. Click the job to view the completed and in-progress steps that Replication Manager takes to complete the job. Here, you can verify whether the first-time setup configuration between the source and destination clusters was successful.
    • Timestamp when the job Started.

    • Timestamp when the job Ended.

    • Duration taken to complete the job.

    • Progress of the job run.

  • On the Actions menu, you can perform the following tasks on the HBase replication policy:
    Option Description
    Edit Enables you to edit the replication policy name or delete one or more tables for the HBase replication policy.
    Delete Removes the HBase replication policy permanently.
    Suspend Pauses an active HBase replication policy. This option appears for target clusters using Cloudera Manager 7.9.0 (Cloudera Manager API version 51) and higher.You can suspend only the specified replication policy for target clusters using Cloudera Manager with API version lower than 45. However, the Suspend option is not available for clusters using Cloudera Manager with API versions 45 through 50.
    Activate Resumes a suspended HBase replication policy. You can activate only the specified suspended policy for target clusters using Cloudera Manager with API version lower than 51.
    View command details Opens the latest HBase replication policy job page. The steps and substeps appear in a tree view. The failed steps are expanded by default, showing 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.

    Retry Create Runs the first-time setup configuration between the source and destination clusters if the first-time setup has failed. This option is available only if the first-time setup configuration fails.
    After you click Retry Create, you can choose:
    • to set an Set HBase Replication Machine User and Sync Replication User to run the first-time setup.
    • to opt for Rolling HBase Service Restart on Source and Rolling HBase Service Restart On Destination after the first-time setup is complete.

    For more information about these options, see Creating HBase replication policy.

    Retry Failed Snapshots Reruns the failed initial snapshots (and only the failed ones) in the replication policy if the Replication Manager failed to replicate the existing data of some tables.

    This option appears if you selected Select Source > Perform Initial Snapshot during policy creation and Replication Manager failed to replicate the existing data. In this scenario, the policy status shows Active with a Snapshot Failure warning message on the Replication Policies page for the HBase replication policy.