tencent cloud

Elastic MapReduce

Release Notes and Announcements
Release Notes
Announcements
Security Announcements
Product Introduction
Overview
Strengths
Architecture
Features
Use Cases
Constraints and Limits
Technical Support Scope
Product release
Purchase Guide
EMR on CVM Billing Instructions
EMR on TKE Billing Instructions
EMR Serverless HBase Billing Instructions
Getting Started
EMR on CVM Quick Start
EMR on TKE Quick Start
EMR on CVM Operation Guide
Planning Cluster
Administrative rights
Configuring Cluster
Managing Cluster
Managing Service
Monitoring and Alarms
TCInsight
EMR on TKE Operation Guide
Introduction to EMR on TKE
Configuring Cluster
Cluster Management
Service Management
Monitoring and Ops
Application Analysis
EMR Serverless HBase Operation Guide
EMR Serverless HBase Product Introduction
Quotas and Limits
Planning an Instance
Managing an Instance
Monitoring and Alarms
Development Guide
EMR Development Guide
Hadoop Development Guide
Spark Development Guide
Hbase Development Guide
Phoenix on Hbase Development Guide
Hive Development Guide
Presto Development Guide
Sqoop Development Guide
Hue Development Guide
Oozie Development Guide
Flume Development Guide
Kerberos Development Guide
Knox Development Guide
Alluxio Development Guide
Kylin Development Guide
Livy Development Guide
Kyuubi Development Guide
Zeppelin Development Guide
Hudi Development Guide
Superset Development Guide
Impala Development Guide
Druid Development Guide
TensorFlow Development Guide
Kudu Development Guide
Ranger Development Guide
Kafka Development Guide
Iceberg Development Guide
StarRocks Development Guide
Flink Development Guide
JupyterLab Development Guide
MLflow Development Guide
Practical Tutorial
Practice of EMR on CVM Ops
Data Migration
Practical Tutorial on Custom Scaling
API Documentation
History
Introduction
API Category
Cluster Resource Management APIs
Cluster Services APIs
User Management APIs
Data Inquiry APIs
Scaling APIs
Configuration APIs
Other APIs
Serverless HBase APIs
YARN Resource Scheduling APIs
Making API Requests
Data Types
Error Codes
FAQs
EMR on CVM
Service Level Agreement
Contact Us

Component Configuration Sharing

PDF
Focus Mode
Font Size
Last updated: 2023-12-27 10:14:00

Overview

You can share the components of an existing cluster with other clusters without deploying such components again. This makes it easier to manage multiple clusters with the same component configurations. Currently supported components include Ranger, ZooKeeper, and Kerberos. Currently supported versions include all EMR versions containing the above components.
Dependent: The current cluster is using components of other existing clusters.
Shared: One or more components of the current cluster are added to other newly created clusters.
Caution
Shared components such as ZooKeeper, Kerberos, and Ranger are no longer deployed in dependent clusters separately, and dependencies cannot be canceled once set. When a cluster with shared components deployed is terminated, all its dependent clusters need to be terminated first. Note that if your account has any overdue payment, dependent clusters won't work properly.

Limits

1. Your account must have the management permissions of one existing cluster.
2. When Kerberos is enabled, other clusters under the current account must have Kerberos deployed before you can enable the dependency.
3. If a dependent component involves user identity management, you need to manually sync the users in the shared cluster to the new cluster after creating it or adding a user. Note that as the current cluster doesn't deploy Kerberos, krb5 users cannot be created.

Service Architecture

Directions

Purchasing a cluster

1. Go to the purchase page and select multiple components under Hadoop.
2. Click Enable and select the shared cluster.
3. After the new cluster is successfully purchased, relevant components will automatically depend on the selected cluster.


Adding a component

1. Select Cluster Service > Add Component on the cluster details page in the console
2. Select the components to be added.
3. Click Enable and select the dependent components and cluster.
4. Click OK and wait for the components to be successfully added to the cluster.

Cluster Information

If a cluster has dependent or shared components, the component information is displayed in Instance info.
Caution
The management features of dependent components can be used only on the Components page of the depended-on cluster.

Account Sync

User accounts need to be created in both the dependent and depended-on clusters.
1. Log in to the depended-on cluster and click Create user to create an account.
2. Log in to the dependent cluster and click Create user to create an account with the same username, user group, and password.
3. The dependent cluster will automatically sync the permission and usage information of the account.


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback