When a Hive replication policy executes in Replication Manager, the admin can monitor the details of the policy and its execution by checking the underlying command details on the source CDH Cluster's CM. In order to export the data and metadata related to the specified Hive tables, multiple steps are executed in the source Cloudera Manager. The Export Hive Metastore section has multiple steps that are explained below:   The first subcommand exports the Hive Metadata for the input database and tables. The next step transfers the HDFS files from the CDH cluster to the cloud storage, which is used by the Data Lake cluster. The next step exports the relevant Sentry permissions. Once the above steps are executed successfully, the workflow resumes on the Data Lake cluster as explained in the previous section.  With these steps, the administration now has a detailed behind-the-scenes view of the steps involved in running a Hive replication policy. ... View more

When a Hive replication policy executes in Replication Manager, the admin can monitor the details of the policy and its execution by checking the underlying command details on the Datalake cluster's CM. An admin can determine further details about the policy by checking “All Recent Commands”. The first step is the Export Metadata step that is performed on the source cluster. This setup in turn exports the data and metadata of the input Hive databases and tables specified in the policy. From the command details, the admin can find logs of the check metadata step. Next is the Import metadata step that updates the Hive database (and table) metadata for a given replication policy. Finally, the last step imports the Exported Sentry permissions into Ranger policies on the Data Lake cluster. If the above steps ran into an error, the admin can determine the specific error by checking the stderr logs of the specific step that ran into an error to troubleshoot the actual error. ... View more

A step-by-step guide that explains the process to register a CDH Cluster as a Classic Cluster is outlined below. This process currently outlines the CDH clusters that aren’t directly visible to the CDP control plane.    Admin needs to select the Classic Cluster tab in the CDP control plane and proceed further with the next steps: CDH Cluster is discovered by its internal IP address which is not visible to the outside world. The wizard provides step-by-step instructions on how to proceed further with the classic cluster registration process. Once the administrator installs the required packages, the admin can verify whether the service is installed and started properly by logging into the CM server host Run the status command to verify whether the service is running properly. Proceed further with the classic cluster registration process. Provide the Cloudera Manager login credentials here. Provide further details such as location, data center name (which is arbitrary) about the CDH cluster. The classic cluster registration process is now complete and the CDH cluster is available to be used as an endpoint in Replication Manager. For each CDH cluster managed by the source Cloudera Manager instance, there will be a separate Classic Cluster entry in the list. These registered Classic Clusters can be further used by different applications such as Replication Manager, Workload Manager and Data Catalog. ... View more