Cloudera Docs

Add source cluster as peer to use in replication policies

You must assign the source cluster as a peer to replicate the data. The Cloudera Manager Server that you are logged into is the destination for replicated data. From the Admin Console of this target Cloudera Manager instance, you designate a peer Cloudera Manager Server as a source from which to replicate data. Therefore, you designate the required source Cloudera Manager instance as a peer in the target Cloudera Manager instance.

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

Adding a peer to use in replication policy

Before you replicate data from source cluster to destination cluster, you must connect the target Cloudera Manager instance with the peer (source Cloudera Manager), and then test the connectivity.

Consider the following points before you add a peer:
  • The required source and target clusters must be healthy and available.
  • If your cluster uses SAML authentication, see Configuring peers with SAML authentication before configuring a peer.
  • Cloudera recommends that TLS/SSL be used. A unknown exception of typejavax.ws.rs.processingexception while connecting to https://[***source.cluster.cmserver***]:7183 warning appears if the URL scheme is HTTP instead of HTTPS.

    After configuring both the peers (source and target Cloudera Manager instances) to use TLS/SSL, add the remote source cluster root CA certificate to the local Cloudera Manager truststore, and vice versa. For more information, see Configuring SSL/TLS certificate exchange between two Cloudera Manager instances

  • When Cloudera Manager is configured with Knox and the source and target clusters are Knox-SSO enabled, ensure that you use the Cloudera Manager port in the peer URL when you add the source and target clusters as peers.

  1. Go to the Cloudera Manager > Replication > Peers page.
    If there are no existing peers, Add Peer appears along with a short message. If peers already exist, they appear in the Peers list.
    The following sample image shows the Peers page:
    The sample image shows the Peers page where you can add a source Cloudera Manager instance as a peer. The page also lists the available peers which were added previously.
  2. Click Add Peer.
  3. In the Add Peer dialog box, provide a name, the peer URL (including the port) of the Cloudera Manager Server source for the data to be replicated, and the login credentials for that server.
    Option Description
    Peer Name Enter a user-friendly name for the source Cloudera Manager instance.
    Peer URL Enter the full URI for the remote source Cloudera Manager instance. This includes the URL and the port of the instance.
    Peer Admin Username Enter a username that is valid on the remote Cloudera Manager. The role assigned to the login user on the source Cloudera Manager server must be User Administrator or Full Administrator.
    Peer Admin Password Enter a password that is valid on the source remote Cloudera Manager.
    Create User With Admin Role Choose to add the peer as an admin peer. This option is mandatory to create Ranger replication policies.
  4. Click Add 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.

Modifying peers to use in replication policy

After you add a replication source as a peer, you can modify or delete the peers as required.

  1. Go to the Cloudera Manager > Replication > Peers page.
  2. Select a peer, and click Actions > Edit.
  3. Update the peer configuration as required, and click Update Peer to save your changes.

Configuring peers with SAML authentication

If your cluster uses SAML Authentication, you can create a Cloudera Manager user account that has the User Administrator or Full Administrator role before you create 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 use this user to create the peer relationship, you can delete the user account after you add the peer.
  2. Create or modify the peer.
  3. Optional: Delete the Cloudera Manager user account that was just created.