Creating a Custom Cluster

Region

Select a region.

Cloud service products in different regions cannot communicate with each other over an intranet. For low network latency and quick access, select the nearest region.

Cluster Name

The cluster name must be unique.

A cluster name can contain 1 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

The default name is mrs_xxxx. xxxx is a random collection of letters and digits.

Cluster Version

Currently, MRS 2.1.1 and MRS 3.0.5 are supported.

Cluster Type

Components

MRS components are as follows.

Metadata

Whether to use external data sources to store metadata.

• Local: Metadata is stored in the local cluster.
• Data connections: Metadata of external data sources is used. If the cluster is abnormal or deleted, metadata is not affected. This mode applies to scenarios where storage and compute are decoupled.

Clusters that support the Hive or Ranger component support this function.

Component

This parameter is valid only when Metadata is set to Data connections. It indicates the type of an external data source. This function is not available in MRS 3.x.

• Hive
• Ranger

Data Connection Type

This parameter is valid only when Metadata is set to Data connections. It indicates the type of an external data source.

• Hive supports the following data connection types:
  • RDS PostgreSQL database
  • RDS MySQL database
  • Local database
• Ranger supports the following data connection types:
  • RDS MySQL database
  • Local database

Data Connection Instance

This parameter is valid only when Data Connection Type is set to RDS PostgreSQL database or RDS MySQL database. This parameter indicates the name of the connection between the MRS cluster and the RDS database. This instance must be created before being referenced here. You can click Create Data Connection to create a data connection. For details, see Configuring Data Connections.

AZ

Select the AZ associated with the region of the cluster.

An AZ is a physical area that uses independent power and network resources. AZs are physically isolated but interconnected through the internal network. This improves the availability of applications. You are advised to create clusters in different AZs.

VPC

A VPC is a secure, isolated, and logical network environment.

Select the VPC for which you want to create a cluster and click View VPC to view the name and ID of the VPC. If no VPC is available, create one.

Subnet

A subnet provides dedicated network resources that are isolated from other networks, improving network security.

Select the subnet for which you want to create a cluster. Click View Subnet to view details about the selected subnet. If no subnet is created in the VPC, go to the VPC console and choose Subnets > Create Subnet to create one. For details about how to configure network ACL outbound rules, see How Do I Configure a Network ACL Outbound Rule?

Security Group

A security group is a set of ECS access rules. It provides access policies for ECSs that have the same security protection requirements and are mutually trusted in a VPC.

When you create a cluster, you can select Auto create from the drop-down list of Security Group to create a security group or select an existing security group.

EIP

After binding an EIP to an MRS cluster, you can use the EIP to access the Manager web UI of the cluster.

When creating a cluster, you can select an available EIP from the drop-down list and bind it. If no EIP is available in the drop-down list, click Manage EIP to access the EIPs service page to one.

Enterprise Project

Select the enterprise project to which the cluster belongs. To use an enterprise project, create one on the Enterprise > Project Management page.

The Enterprise Management console of the enterprise project is designed for resource management. It helps enterprises manage cloud-based personnel, resources, permissions, and finance in a hierarchical manner, such as management of companies, departments, and projects.

CPU Architecture

CPU architecture supported by MRS:

• x86: The x86-based CPU architecture uses Complex Instruction Set Computing (CISC). Each instruction can be used to execute low-level hardware operations. The number of instructions is large, and the length of each instruction is different. Therefore, executing such an instruction is complex and time-consuming.
• Kunpeng: The Kunpeng-based CPU architecture uses Reduced Instruction Set Computing (RISC). RISC is a microprocessor that executes fewer types of computer instructions but at a higher speed than CISC. RISC simplifies the computer architecture and improves the running speed. Compared with the x86-based CPU architecture, the Kunpeng-based CPU architecture has a more balanced performance and power consumption ratio. Kunpeng features high density, low power consumption, high cost-effectiveness.

Common Template

This parameter is valid only when Cluster Type is set to Custom. For details, see Custom Cluster Template Description.

Node Type

MRS provides three types of nodes:

• Master: A Master node in an MRS cluster manages the cluster, assigns executable cluster files to Core nodes, traces the execution status of each job, and monitors the DataNode running status.
• Core: A Core node in a cluster processes data and stores process data in HDFS. Analysis Core nodes are created in an analysis cluster. Streaming Core nodes are created in a streaming cluster. Both analysis and streaming Core nodes are created in a hybrid cluster.
• Task: A Task node in a cluster is used for computing and does not store persistent data. Yarn and Storm are mainly installed on Task nodes. Task nodes are optional, and the number of Task nodes can be zero. Analysis Task nodes are created in an analysis cluster. Streaming Task nodes are created in a streaming cluster. Both analysis and streaming Task nodes are created in a hybrid cluster.
  When the data volume change is small in a cluster but the cluster's service processing capabilities need to be remarkably and temporarily improved, add Task nodes to address the following situations:

  • Service volumes temporarily increase, for example, report processing at the end of the year.
  • Long-term tasks must be completed in a short time, for example, some urgent analysis tasks.

Instance Specifications

Instance specifications of Master or Core nodes. MRS supports host specifications determined by CPU, memory, and disk space. Click to configure the instance specifications, system disk, and data disk parameters of the cluster node.

System Disk

Storage type and storage space of the system disk on a node.

Data Disk

Data disk storage space of a node. To increase data storage capacity, you can add disks at the same time when creating a cluster. The following two application scenarios are involved.

• Data storage and computing are separated. Data is stored in OBS, which features low cost and unlimited storage capacity. The clusters can be terminated at any time in OBS. The computing performance is determined by OBS access performance and is lower than that of HDFS. This configuration is recommended if data computing is infrequent.
• Data storage and computing are not separated. Data is stored in HDFS, which features high cost, high computing performance, and limited storage capacity. Before terminating clusters, you must export and store the data. This configuration is recommended if data computing is frequent.

The storage type can be any of the following:

• SATA: common I/O
• SAS: high I/O
• SSD: ultra-high I/O
• GPSSD: general-purpose SSD

Instance Count

Number of Master and Core nodes.

For Master nodes:

• If Cluster HA is enabled, the number of Master nodes is fixed to 2.
• If Cluster HA is disabled, the number of Master nodes is fixed to 1.

At least one Core node must exist and the total number of Core and Task nodes cannot exceed 500.

Task: Click to add a Task node. Click to modify the instance specifications and disk configuration of a Task node. Click to delete the added Task node.

LVM

This parameter is valid when a streaming Core node is created only. Click this parameter to enable or disable the disk LVM management function. This parameter is not available in MRS 3.x and later versions.

If LVM is enabled, all disks on a node are mounted as logical volumes. This delivers more proper disk planning to avoid data skew, thereby improving system stability.

Topology Adjustment

If the deployment mode in the Common Node does not meet the requirements, set Topology Adjustment to Enable and adjust the instance deployment mode based on service requirements. For details, see Topology Adjustment for a Custom Cluster. This parameter is valid only when Cluster Type is set to Custom.

Tag

For details, see Adding a Tag to a Cluster.

Hostname Prefix

Enter the prefix for the computer hostname of an ECS in the cluster.

Auto Scaling

Auto scaling can be configured only after you specify Task node specifications in the Configure Hardware step. For details about how to configure Task node specifications, see Configuring an Auto Scaling Rule.

Bootstrap Action

For details, see Adding a Bootstrap Action. This parameter is not available in MRS 3.x.

Agency

By binding an agency, ECSs or BMSs can manage some of your resources. Determine whether to configure an agency based on the actual service scenario.

For example, you can configure an agency of the ECS type to automatically obtain the AK/SK to access OBS. For details, see Configuring a Storage-Compute Decoupled Cluster (Agency).

The MRS_ECS_DEFAULT_AGENCY agency has the OBSOperateAccess permission of OBS and the CESFullAccess (for users who have enabled fine-grained policies), CES Administrator, and KMS Administrator permissions in the region where the cluster is located.

Metric Sharing

Monitoring metrics of big data components are collected. If a fault occurs when you use a cluster, share the monitoring metrics withtechnical support personnel for troubleshooting. This parameter is not available in MRS 3.x.

OBS Permission Control

Users who have enabled fine-grained permission control can use this function to grant permissions on different directories in OBS file systems to different MRS users. For details, see Configuring Fine-Grained Permissions for MRS Multi-User Access to OBS. This parameter is not available in MRS 3.x.

Data Disk Encryption

Whether to encrypt data in the data disk mounted to the cluster. This function is disabled by default. To use this function, you must have the Security Administrator and KMS Administrator permissions. This parameter is not available in MRS 3.x.

Keys used by encrypted data disks are provided by the Key Management Service (KMS) of the Data Encryption Workshop (DEW), secure and convenient. Therefore, you do not need to establish and maintain the key management infrastructure.

Click Data Disk Encryption to enable or disable the data disk encryption function.

Key ID

This parameter is displayed only when the Data Disk Encryption function is enabled. This parameter indicates the key ID corresponding to the selected key name. This parameter is not available in MRS 3.x.

Key Name

This parameter is mandatory when the Data Disk Encryption function is enabled. Select the name of the key used to encrypt the data disk. By default, the default master key named evs/default is selected. You can select another master key from the drop-down list. This parameter is not available in MRS 3.x.

If disks are encrypted using a CMK, which is then disabled or scheduled for deletion, the disks can no longer be read from or written to, and data on these disks may never be restored. Exercise caution when performing this operation.

Click View Key List to enter a page where you can create and manage keys.

Alarm

If the alarm function is enabled, the cluster maintenance personnel can be notified in a timely manner to locate faults when the cluster runs abnormally or the system is faulty.

Rule Name

Name of the rule for sending alarm messages. The value can contain only digits, letters, hyphens (-), and underscores (_).

Topic Name

Select an existing topic or click Create Topic to create a topic. To deliver messages published to a topic, you need to add a subscriber to the topic. For details, see Adding Subscriptions to a Topic.

A topic serves as a message sending channel, where publishers and subscribers can interact with each other.

Kerberos Authentication

Whether to enable Kerberos authentication when logging in to Manager.

• : If Kerberos Authentication is disabled, common users can use all functions of an MRS cluster. You are advised to disable Kerberos authentication in single-user scenarios.
• : If Kerberos Authentication is enabled, common users cannot use the file and job management functions of an MRS cluster and cannot view cluster resource usage or the job records for Hadoop and Spark. To use more cluster functions, the users must contact the Manager administrator to assign more permissions. You are advised to enable Kerberos authentication in multi-user scenarios.

Username

Name of the administrator of Manager. admin is used by default.

Password

Password of the Manager administrator

The following requirements must be met:

• Must contain 8 to 26 characters.
• Must contain at least four of the following:
  • Lowercase letters
  • Uppercase letters
  • Digits
  • Have at least one of the following special characters: !?,.: -_{} [ ]@ $% ^ + = /
• Cannot be the same as the username or the username spelled backwards.

Password Strength: The colorbar in red, orange, and green indicates weak, medium, and strong password, respectively.

Confirm Password

Enter the password of the Manager administrator again.

Login Mode

• Password

  You can log in to ECS nodes using a password.

  A password must meet the following requirements:

  1. Must be a string and 8 to 26 characters long.
  2. The password must contain at least four types of the following characters: uppercase letters, lowercase letters, digits, and special characters (! ?,.: -_{} [ ]@ $% ^ + = /).
  3. The password cannot be the username or the reverse username.
• Key Pair

  Key pairs are used to log in to ECS nodes of the cluster. Select a key pair from the drop-down list. Select "I acknowledge that I have obtained private key file SSHkey-xxx and that without this file I will not be able to log in to my ECS." If you have never created a key pair, click View Key Pair to create or import a key pair. And then, obtain a private key file.

  A key pair, also called an SSH key, consists of a public key and a private key. You can create an SSH key and download the private key for authenticating remote login. For security, a private key can only be downloaded once. Keep it secure.

  Use an SSH key in either of the following two methods:

  1. Creating an SSH key: After you create an SSH key, a public key and a private key are generated. The public key is stored in the system, and the private key is stored in the local ECS. When you log in to an ECS, the public and private keys are used for authentication.
  2. Importing an SSH key: If you have obtained the public and private keys, import the public key into the system. When you log in to an ECS, the public and private keys are used for authentication.

Secure Communications

MRS clusters provision, manage, and use big data components through the management console. Big data components are deployed in a user's VPC. If the MRS management console needs to directly access big data components deployed in the user's VPC, you need to enable the corresponding security group rules after you have obtained user authorization. This authorization process is called secure communications. For details, see Communication Security Authorization.

If the secure communications function is not enabled, MRS clusters cannot be created.

MRS.101

Insufficient quota to meet your request. Contact customer service to increase the quota.

MRS.102

The token cannot be null or invalid. Try again later or contact customer service.

MRS.103

Invalid request. Try again later or contact customer service.

MRS.104

Insufficient resources. Try again later or contact customer service.

MRS.105

Insufficient IP addresses in the existing subnet. Try again later or contact customer service.

MRS.201

Failed due to an ECS error. Try again later or contact customer service.

MRS.202

Failed due to an IAM error. Try again later or contact customer service.

MRS.203

Failed due to a VPC error. Try again later or contact customer service.

MRS.400

MRS system error. Try again later or contact customer service.