Cloudera Enterprise 5.15.x | Other versions

Designating a Replication Source

Minimum Required Role: Cluster Administrator (also provided by Full Administrator)

The Cloudera Manager Server that you are logged into is the destination for replications set up using that Cloudera Manager instance. From the Admin Console of this destination Cloudera Manager instance, you can designate a peer Cloudera Manager Server as a source of HDFS and Apache Hive data for replication.

Configuring a Peer Relationship

  Note: If your cluster uses SAML Authentication, see Configuring Peers with SAML Authentication before configuring a peer.
  1. Go to the Peers page by selecting Backup > Peers. If there are no existing peers, you will see only an Add Peer button in addition to a short message. If peers already exist, they display in the Peers list.
  2. Click the Add Peer button.
  3. In the Add Peer dialog box, provide a name, the URL (including the port) of the Cloudera Manager Server source for the data to be replicated, and the login credentials for that server.
      Important: The role assigned to the login on the source server must be either a User Administrator or a Full Administrator.
    Cloudera recommends that TLS/SSL be used. A warning is shown if the URL scheme is http instead of https. After configuring both peers to use TLS/SSL, add the remote source Cloudera Manager TLS/SSL certificate to the local Cloudera Manager truststore, and vice versa. See Configuring TLS Encryption for Cloudera Manager.
  4. Click the Add Peer button in the dialog box to create the peer relationship.

    The peer is added to the Peers list. Cloudera Manager automatically tests the connection between the Cloudera Manager Server and the peer. You can also click Test Connectivity to test the connection. Test Connectivity also tests the Kerberos configuration for the clusters. For more information about this part of the test, see Kerberos Connectivity Test.

Modifying Peers

  1. Go to the Peers page by selecting Backup > Peers. If there are no existing peers, you will see only an Add Peer button in addition to a short message. If peers already exist, they display in the Peers list.
  2. Do one of the following:
    • Edit
      1. In the row for the peer, select Edit.
      2. Make your changes.
      3. Click Update Peer to save your changes.
    • Delete - In the row for the peer, click Delete.

HDFS and Hive/Impala Replication To and From Amazon S3 or Microsoft ADLS

Minimum Required Role: User Administrator (also provided by Full Administrator)

To configure Amazon S3 or Microsoft ADLS as a source or destination for HDFS or Hive/Impala replication, you configure AWS Credentials or Azure Credentialsthat specify the type of authentication to use, the Access Key ID, and Secret Key. See How to Configure AWS Credentials or Configuring ADLS Access Using Cloudera Manager.

After adding the AWS or Azure credentials, you can click the Replication Schedules link to define a replication schedule. See HDFS Replication or Hive/Impala Replication for details about creating replication schedules. You can also click Close and create the replication schedules later. Select the AWS or Azure Credentials account in the Source or Destination drop-down lists when creating the schedules.

Configuring Peers with SAML Authentication

If your cluster uses SAML Authentication, do the following before creating a peer:
  1. Create a Cloudera Manager user account that has the User Administrator or Full Administrator role.

    You can also use an existing user that has one of these roles. Since you will only use this user to create the peer relationship, you can delete the user account after adding the peer.

  2. Create or modify the peer, as described in this topic.
  3. (Optional) Delete the Cloudera Manager user account you just created.
Page generated May 18, 2018.