Using HBase replication policies

To create a HBase replication policy, you must register the on-premises cluster (CDH or CDP Private Cloud Base) as a classic cluster in Management Console, register cloud account credentials in the Replication Manager service, verify cluster access, and configure minimum ports for replication. When you create the first HBase replication policy to replicate HBase data from a source cluster to a target cluster, the Replication Manager performs the first-time setup configuration steps and then replicates the data.

The first-time setup configuration steps include creating peers between the source (ClusterA) and target cluster (ClusterB) and initiating required configuration changes, and HBase service restarts on both the clusters. However, if you are replicating HBase data from on-premises cluster to Cloudera Operational Database (COD) or Data Hub, you must manually restart HBase service on the source cluster. Subsequent HBase replication policies for the same cluster pair (ClusterA and ClusterB) do not require a first-time setup.

You can create new HBase replication policies between two clusters even when the first-time setup between them is in progress. Replication Manager does not allow you to use a cluster in a cluster pair (ClusterA and ClusterB) that has at least one active HBase replication policy between them with another cluster to create an HBase replication policy. However, if no active policies exist between the cluster pair (inactive cluster pair), Replication Manager allows you to use them with other clusters to create HBase replication policies. When you use one of the clusters in an inactive cluster pair during policy creation, Replication Manager shows a warning message notifying that the chosen cluster is part of an existing cluster pair which would be broken to create a new cluster pair.

When HBase replication policies are created, modified, or deleted simultaneously, Replication Manager processes each operation independent of each other.