E-MapReduce (EMR) clusters are independent of each other. The client of a cluster can access only the namespaces that are configured in the cluster. If you have multiple clusters, you can configure JindoFS parameters to implement cross-cluster access to JindoFS. This topic describes how to implement cross-cluster access to JindoFS. Cluster A and Cluster B are used as an example.
Prerequisites
- EMR clusters A and B of the 3.30.0 version or later are deployed in the same VPC. For information about how to create a cluster, see Create a cluster.
- The /etc/hosts file is configured to synchronize the data of the hosts of all nodes in Cluster B to Cluster A.
Modify configurations
Associate multiple clusters
To associate multiple clusters, use client.external.namespace.rpc.addresses to configure remote addresses for these clusters. Separate the addresses with semicolons (;).
For example, the address of Cluster B is emr-header-1.<cluster-B>:8101
, and namespace.backend.type is set to rocksdb for Cluster B. The address of Cluster
C is emr-header-1.<cluster-C>:8101,emr-header-2.<cluster-C>:8101,emr-header-3.<cluster-C>:8101
, and namespace.backend.type is set to raft for Cluster C. To associate Cluster B
and Cluster C with Cluster A, set Key to client.external.namespace.rpc.addresses and
Value to emr-header-1.<cluster-B>:8101;emr-header-1.<cluster-C>:8101,emr-header-2.<cluster-C>:8101,emr-header-3.<cluster-C>:8101
in the Add Configuration Item dialog box for Cluster A.