What's new

This section lists major features and updates for Replication Manager service.

April 2024

CDP version 7.2.18 introduces the following new features in the Replication Manager service.

Register GCP credentials

You can add the GCP credentials on the CDP Public Cloud Replication Manager > Cloud Credentials page to use in Replication Manager.

For more information, see Registering GCS credentials to use in Replication Manager.

HBase replication policy enhancements

HBase replication policies support the following enhancements:

  • You can create multiple HBase replication policies between multiple clusters to replicate HBase data.

    For more information, see Replicate HBase data simultaneously between multiple clusters.

  • You can choose to Replicate all user tables or Replicate only tables where replication is already enabled after you choose the Select Source > Replicate Database option during the HBase replication policy creation process.

    The Replicate only tables where replication is already enabled option is supported only if the target cluster uses Cloudera Manager version 7.12.0.0 and higher, 7.11.0-h3 and higher, or 7.9.0-h7 and higher.

    For more information, see Methods to replicate HBase data and Creating HBase replication policies.

  • You can enter a YARN Queue Name to submit the replication job during the HBase replication policy creation or choose to retain the "default" value.

    For more information, see Creating HBase replication policies.

  • You can click Actions on the Replication Policies page to Collect diagnostic bundle for the required HBase replication policy.

    For more information, see Monitor HBase replication policy job details.

For more information about feature support in CDP Public Cloud Replication Manager, see Supported features.

January 2024

This release of the Replication Manager service introduces the following new features.

Replicate HBase tables in a database depending on the replication scope

During the HBase replication policy creation process, after you select the Select Source > Replicate Database, you can choose the Select Source > Replicate all user tables option to replicate all the HBase tables in the database, or choose the Select Source > Replicate only tables where replication is already enabled option to replicate the tables for which the replication scope is already set to 1. This provides a choice to replicate the required tables in a database.

The Replicate only tables where replication is already enabled option is supported only if the target cluster CDP version is CDP version 7.2.16.500 using Cloudera Manager 7.9.0-h7 or higher versions, CDP version 7.2.17.300 using Cloudera Manager 7.11.0-h3 or higher versions, or CDP version 7.2.18 using Cloudera Manager 7.12.0.0.

For more information, see Methods to replicate HBase data and Creating HBase replication policies.

Replicate HBase data between multiple clusters simultaneously

Starting from CDP Public Cloud version 7.2.16.500, 7.2.17.200, and 7.2.18 you can create multiple HBase replication policies between multiple clusters to replicate HBase data.

For more information, see Replicate HBase data simultaneously between multiple clusters.

August 2023

This release of the Replication Manager service introduces the following new features.

Replicate HBase data in all the tables in a database

You can replicate HBase data (existing tables and future tables in a database) using the Select Source > Replicate Databases option during the HBase replication policy creation process. You can use this option only if the minimum target Cloudera Manager version is 7.11.0 and the minimum source cluster versions are CDH 5.16.2 (after you upgrade the source cluster Cloudera Manager), CDP Private Cloud Base 7.1.6, or COD 7.2.17.

For more information, see HBase replication policy and Creating HBase replication policies.

Provide a unique replication policy name

You must provide a unique name to the replication policy during the replication policy creation process if the Cloudera Manager API version is 51 or higher.

For other Cloudera Manager API versions, you can continue to use an existing replication policy with an empty name. However, if you edit the replication policy and provide a name for the replication policy, ensure that the name conforms to the validation rules.

For more information, see Managing HDFS replication policy, Managing Hive replication policy, or Managing HBase replication policy.

Load replication policies and their job history on the Replication Policies page

You can choose one of the following options to Load policies faster by delaying to load their job history:

  • Delay loading job history when history is too long
  • Always load job history
  • Never load job history

By default, the replication policies are loaded only partially on the Replication Policies page, therefore the page might display incomplete statistics about a job status and replication policies with failed jobs might take a longer time to load. You can change the behavior depending on your requirements.

For more information, see Replication Policies page