No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionInsight HD 6.5.0 Administrator Guide 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Enabling Cross-Cluster Replication

Enabling Cross-Cluster Replication

Scenario

DistCp is used to copy the data stored on HDFS from the FusionInsight HD cluster to another cluster. DistCp depends on the cross-cluster replication function, which is disabled by default. This function needs to be enabled in the two clusters.

Modify parameters on FusionInsight Manager to enable the cross-cluster replication function.

Impact on the System

Yarn needs to be restarted to enable the cross-cluster replication function and cannot be accessed during the restart.

Prerequisites

hadoop.rpc.protection of the two HDFS clusters must be set to the same data transmission mode. The privacy indicates that the channels are encrypted by default. The authentication indicates that channels are not encrypted.

Procedure

  1. Log in to FusionInsight Manager of a cluster.
  2. Choose Cluster > Service > Yarn > Configuration > All Configurations.
  3. In the navigation tree, choose Yarn > Distcp.
  4. Set dfs.namenode.rpc-address.haclusterX.remotenn1 to the service IP address and RPC port number of one NameNode instance of the peer cluster, and set dfs.namenode.rpc-address.haclusterX.remotenn2 to the service IP address and RPC port number of the other NameNode instance of the peer cluster.

    dfs.namenode.rpc-address.haclusterX.remotenn1 and dfs.namenode.rpc-address.haclusterX.remotenn2 do not distinguish active and standby NameNode instances. The default NameNode RPC port number is 25000 and cannot be modified on FusionInsight Manager.

    Examples of modified parameter values: 10.1.1.1:25000 and 10.1.1.2:25000.

    If the Federation is configured in the peer cluster with multiple pairs of NameNodes (multiple NameServices), here you can only configure the RPC addresses of the two NameNodes in one of the NameService. Configuring the RPC addresses of two NameNodes that do not belong to the same NameService is prohibited.

  5. Click Save, and click OK.
  6. Restart Yarn.
  7. Log in to FusionInsight Manager of the other cluster and repeat Step 2 to Step 6.
Download
Updated: 2019-05-17

Document ID: EDOC1100074522

Views: 6194

Downloads: 12

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next