Release Notes
Announcements
Security Announcements
Configuration Item | Configuration Items Description |
Cluster name | Set the cluster name to distinguish between different EMR clusters. The system generates a random name, which can be modified. |
Region | The physical data center where the cluster is deployed. Each region represents an independent physical data center, and private networks of CVMs between different regions are not interconnected. Note: 1. Once the cluster is created, the region cannot be changed, so choose carefully. 2. Only container clusters within this region are supported to provide resources for the cluster. |
Container type | 1. The service role is deployed by using resources provided by the container layer, supporting both TKE General and TKE Serverless clusters. 2. The computing resources are container deployment resources purchased synchronously with EMR, supporting resource association for EMR on TKE clusters. Note: Select a specific container cluster or computing resource to provide Pod resources for service deployment of the EMR on TKE cluster. |
Cluster Network | Used for purchasing a db. It is necessary to ensure that the EMR cluster network is consistent with the container cluster network. |
AZ and subnet | Used for purchasing a db. It is necessary to ensure that the EMR cluster network is consistent with the container cluster network. |
Security group | The security group functions as a firewall to configure network access control for CVM. If no security group is available, EMR will automatically create one for you. If there is an existing security group in use, you can select it directly. If the number of security groups has reached the upper limit and new ones cannot be created, you can delete some unused security groups. View the security groups currently in use. Create a security group: EMR helps users create a security group. By default, port 30002 and the necessary IP ranges for private network communication are enabled. Existing EMR security group: Select an already created EMR security group as the security group for the current instance. The security group should have the necessary IP ranges for private network communication enabled. |
Billing mode | Only supports pay-as-you-go mode. Pay-as-you-go: Pay based on usage duration. Account identity verification is required, and a 2-hour fee will be frozen at the time of activation (vouchers cannot be used as a freezing deposit). The frozen resource fee will be refunded upon termination. |
Cluster Type | Both data lake and machine learning cluster types are supported. Choose the one according to the actual business needs for cluster creation. The default is the data lake cluster type. |
Product version | The components and their versions bundled with different product versions vary. |
Deploy task | Optional components that can be customized and combined based on your needs. Select at least one component service for deployment. Supported deployment types: default deployment and associated deployment. Associated deployment: Provides service sources for the current cluster, such as other cloud EMR clusters or DLC. Default deployment: Deploys the current service to the selected container resources, allowing customization of resource specifications and quantity (service role level deployment). Recommended for use. |
Associated deployment | Select an EMR on CVM or EMR on TKE cluster that contains the current service. 1. When you select an EMR on CVM cluster, the cluster needs to have the current service deployed. 2. When you select an EMR on TKE cluster, the current service in the cluster needs to be configured to provide external services. 3. MetaStore (HiveMetaStore) supports selecting DLC as the service source. |
Default deployment | Data volume directory: Provides data storage directories for containers. Currently, only mounting with HostPath or using the created PVC is supported. Pod specifications set service role dimension deployment information as an optional setting. External access setting: Set whether the current role provides external services, with optional support for public network LB access and private network LB access. Node scheduling policy: Set the scheduling policy for the current role deployment, allowing Pods to be scheduled to nodes that match the desired Label according to the scheduling rules. |
Hive metadatabase | If the Hive component is selected, Hive Metastore offers two storage options: The first option is automatic creation, where Hive metadata is stored in an independently purchased MetaDB instance for the cluster. The second option is to associate an external Hive Metastore, where you can choose to link to EMR-MetaDB or a self-built MySQL database, with metadata stored in the associated database, which will not be destroyed when the cluster is terminated. See Hive Metadata Management. Note: When you select one or more of the following components such as Hue, Ranger, Oozie, Druid, and Superset, the system will automatically purchase a MetaDB for storing metadata of components other than Hive. |
COS bucket | Used for storing logs, JAR packages, and other information. |
Tag | You can add tags to cluster or node resources during creation to facilitate resource management. A maximum of 5 tags can be added, and tag keys should not be duplicated. |
Set Password | Set the webUI password. The current password is only used to initially set up the service webUI access password. |
Terms of agreement |
피드백