Configuring a peer to use in replication policy

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

If your cluster uses SAML Authentication, see Configuring peers with SAML authentication before configuring a peer.

  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.
  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 Cloudera Manager instance.
    Peer URL Enter the full URI for the remote Cloudera Manager instance.
    Peer Admin Username Enter a username that is valid on the remote Cloudera Manager.
    Peer Admin Password Enter a password that is valid on the 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.

    Cloudera recommends that TLS/SSL be used. A unknown exception of type while connecting to https://[***source.cluster.cmserver***]:7183 warning appears if the URL scheme is http instead of https. After configuring both peers 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.
  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.