Help Center > > User Guide> Configuring Clusters> Custom Purchase of a Cluster

Custom Purchase of a Cluster

Updated at: Apr 28, 2020 GMT+08:00

The first step of using MRS is to purchase a cluster. This section describes how to create a cluster on the Custom Config tab of the MRS management console.

You can create an IAM user or user group on the IAM management console and grant it specific operation permissions, to perform refined resource management, after registering a HUAWEI CLOUD account. For details, see Permission Management.

  1. Log in to the MRS management console.
  2. Click Buy Cluster. The Buy Cluster page is displayed.

    When creating a cluster, pay attention to quota notification. If a resource quota is insufficient, increase the resource quota as prompted and create a cluster.

  3. On the Buy Cluster page, click the Custom Config tab.
  4. Configure cluster information by referring to Software Configuration and click Next Configure Hardware.
  5. Configure cluster information by referring to Hardware Configuration and click Next Set Advanced Options.
  6. Set advanced options by referring to (Optional) Advanced Configuration and click Buy Now.

    For any doubt about the pricing, click Pricing Details in the lower left corner.

  7. Click Back to Cluster List to view the cluster status.

    For details about cluster status during creation, see the description of the status parameters in Table 1.

    It takes some time to create a cluster. The initial status of the cluster is Starting. After the cluster has been created successfully, the cluster status becomes Running.

    On the MRS management console, a maximum of 10 clusters can be concurrently created, and a maximum of 100 clusters can be managed.

Software Configuration

Table 1 MRS cluster software configuration




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

Cluster name, which is globally unique.

A cluster name can contain only 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 1.8.10, MRS 1.9.2, and MRS 2.1.0 are supported. The latest version of MRS is used by default.

Cluster Type

There are three types of clusters:
  • Analysis cluster: is used for offline data analysis and provides Hadoop components.
  • Streaming cluster: is used for streaming tasks and provides stream processing components.
  • Hybrid cluster: is used for both offline data analysis and streaming processing and provides Hadoop components and streaming processing components. You are advised to use a hybrid cluster to perform offline data analysis and streaming processing tasks at the same time. (MRS 1.8.5 or later supports hybrid clusters.)

MRS streaming clusters do not support job and file management functions.


The MRS components are as follows:

Components of an analysis cluster:
  • Presto: open source and distributed SQL query engine
  • Hadoop: distributed system architecture
  • Spark: in-memory distributed computing framework
  • Hive: data warehouse framework built on Hadoop
  • OpenTSDB: a distributed, scalable time series database that can store and serve massive amounts of time series data without losing granularity
  • HBase: distributed column-oriented database
  • Tez: provides a distributed computing framework of directed acyclic graphs (DAGs). (supported in MRS 1.9.2 or later)
  • Hue: provides the Hadoop UI capability, which enables users to analyze and process Hadoop cluster data on browsers
  • Loader: a tool based on source Sqoop 1.99.7, designed for efficiently transferring bulk data between Apache Hadoop and structured datastores such as relational databases

    Hadoop is mandatory, and Spark and Hive must be used together. Select components based on service requirements.

  • Flink: a distributed big data processing engine that can perform stateful computations over both finite and infinite data streams
  • Alluxio: a memory speed virtual distributed storage system.
  • Ranger: a framework to enable, monitor, and manage data security across the Hadoop platform. (Currently, Ranger does not support Kerberos authentication.)
  • Impala: an SQL query engine for processing huge volumes of data. (supported in MRS 2.1.0 or later)
  • Kudu: a column-oriented data store. (supported in MRS 2.1.0 or later)
Components of a streaming cluster:
  • Kafka: distributed messaging system
  • KafkaManager: Kafka cluster monitoring management tool (supported in MRS 1.8.10 and MRS 1.9.2)
  • Storm: distributed real-time computing system
  • Flume: distributed, reliable, and available service for efficiently collecting, aggregating, and moving large amounts of log data

Use External Data Sources to Store Metadata

Whether to use external data sources to store metadata. Click to enable this function. If this function is enabled, metadata will not be affected if a cluster is abnormal or deleted. This function applies to scenarios where storage and computing are separated.

MRS 1.9.2 or later supports this function.

Data Connection Type

This parameter is valid only when Use External Data Sources to Store Metadata is enabled. It indicates the type of an external data source.

  • Hive supports the following data connection types:
    • RDS PostgreSQL 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 Managing Data Connections.

Kerberos Authentication

Whether to enable Kerberos authentication when logging in to MRS Manager.

  • : If Kerberos authentication is disabled, you can use all functions of an MRS cluster. You are advised to disable Kerberos authentication in single-user scenarios. If Kerberos authentication is disabled, you can follow instructions in Security Configuration Suggestions for Clusters with Kerberos Authentication Disabled to perform security configuration.
  • : 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 MRS Manager administrator to assign more permissions. You are advised to enable Kerberos authentication in multi-user scenarios.

You can click or to disable or enable Kerberos authentication, respectively.

If the Ranger component is selected, Kerberos authentication cannot be enabled.


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


Password of the MRS Manager administrator

The following requirements must be met:

  • Must contain 8 to 32 characters.
  • Must contain at least three of the following:
    • Lowercase letters
    • Uppercase letters
    • Digits
    • Special characters: `~!@#$%^&*()-_=+\|[{}];:'",<.>/?
    • Spaces
  • Must be different from the username.
  • Cannot be the same as 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 MRS Manager administrator again.

Hardware Configuration

Table 2 MRS cluster hardware configuration



Billing Mode

MRS provides two billing modes.
  • Yearly/Monthly
  • Pay-per-use

Required Duration

This parameter is valid in Yearly/Monthly billing mode and indicates a cluster subscription duration. The minimum duration is 1 month and the maximum duration is 1 year.

If Auto-renew is selected, monthly subscriptions are automatically renewed every month and yearly subscriptions are automatically renewed every year.


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.


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.


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 to enter the VPC and view the name and ID of the subnet. If no subnet is created under the VPC, click Create Subnet to create one.


Do not associate the subnet with the network ACL.

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 an MRS 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.


When you select a security group created by yourself, ensure that the inbound rule contains a rule in which Protocol is set to All, Port is set to All, and Source is set to a trusted accessible IP address range. Do not use as a source address. Otherwise, security risks may occur. If you do not know the trusted accessible IP address range, select Auto create.


After binding an EIP to an MRS cluster, you can use the EIP to access the MRS Manager page 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 purchase one.


The EIP must be in the same region as the cluster.

Enterprise Project

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

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.

Table 3 Cluster node information



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.

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 number of clusters does not change much but the clusters' 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.

Billing Mode

Billing mode of nodes in a cluster.

  • The billing mode of Master and Core nodes is the same as that of the cluster.
  • The billing mode of Task nodes is fixed to Pay-per-use, that is, Task nodes in a yearly/monthly subscribed cluster are still billed in a pay-per-use basis.

Instance Specifications

Instance specifications of Master or Core nodes. MRS supports host specifications determined by CPU, memory, and disk space. For details about instance specifications, see ECS Specifications Used by MRS and BMS Specifications Used by MRS. Click Modify to configure the instance specifications and data disk parameters of cluster nodes.

MRS supports BMS specifications only when the billing mode of a cluster is Yearly/Monthly.

MRS supports the following hybrid deployment of ECSs and BMSs:

  • Master, Core, and Task nodes are deployed on ECSs.
  • Master and Core nodes are deployed on BMSs, and Task nodes are deployed on ECSs.
  • Master nodes are deployed on either ECSs or BMSs, Core nodes are deployed on either ECSs or BMSs, and Task nodes are deployed on ECSs.

Tenants share physical resources of ECSs, but can exclusively use resources of BMSs. BMSs can better meet your requirements for deploying key applications and services that require high performance (such as big data clusters and enterprise middleware systems) and a secure and reliable running environment.

If BMS specifications are used, Master node specifications cannot be scaled up.

  • More advanced instance specifications provide better data processing. However, they require higher cluster cost.
  • If you select HDDs for Core nodes, there is no charging information for data disks. The fees are charged with ECSs.
  • If you select HDDs for Core nodes, the system disks (40 GB) of Master nodes and Core nodes, as well as the data disks (200 GB) of Master nodes, are SATA disks.
  • If you select non-HDD disks for Core nodes, the disk types of Master and Core nodes are determined by Data Disk.
  • If Sold out appears next to an instance specification of a node, the node of this specification cannot be purchased. You can only purchase nodes of other specifications.
  • The Master node specification (4 vCPUs 8 GB) is not within the SLA after-sales scope. It is applicable only to the test environment and is not recommended for the production environment.

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.

Currently, SATA, SAS, and SSD storage types are supported.

  • SATA: Common I/O
  • SAS: High I/O
  • SSD: Ultra-high I/O

Value range: 100 GB to 32,000 GB

  • More nodes in a cluster require higher disk capacity of Master nodes. To ensure stable cluster running, set the disk capacity of the Master node to over 600 GB if the number of nodes is 300 and increase it to over 1 TB if the number of nodes reaches 500.
  • The Master node increases data disk storage space for MRS Manager. The disk type must be the same as the data disk type of Core nodes. The default disk space is 200 GB and cannot be changed.

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.

  • A maximum of 500 Core nodes are supported by default. If more than 500 Core nodes are required, increase the quota. For details, see Quotas.
  • A small number of nodes may cause clusters to run slowly while a large number of nodes may be unnecessarily costly. Set an appropriate value based on data to be processed.

Cluster HA

Whether to enable high availability for a cluster. This parameter is enabled by default.

If you enable this option, the management processes of all components will be deployed on both Master nodes to achieve hot standby and prevent single-node failure, improving reliability. If you disable this option, they will be deployed on only one Master node. As a result, if a process of a component becomes abnormal, the component will fail to provide services.

  • : Disabled. When Cluster HA is disabled, there is only one Master node and the number of Core nodes is three by default. However, you can decrease the number of Core nodes to 1.
  • : Enabled. When Cluster HA is enabled, there are two Master nodes and the number of Core nodes is three by default. However, you can decrease the number of Core nodes to 1.

You can click or to disable or enable high availability, respectively.

Disk LVM

This parameter is valid in the Operation column of a streaming Core node only when the streaming Core node is created. Click this parameter to enable or disable the disk LVM function. The function status is displayed in the parentheses next to this parameter.

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.


  • Configure: Configure Task nodes.
  • Delete: Delete the existing Task nodes.
Table 4 Login mode



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 32 characters long.
    2. Must contain at least three of the following: uppercase letters, lowercase letters, digits, special characters (`~!@#$%^&*()-_=+\|[{}];:'",<.>/?), and spaces.
    3. Cannot be the username or the username spelled backwards.
  • Key Pair

    Key pairs are used to log in to ECS nodes of the cluster. Select a key pair form the drop-down list. Select "I acknowledge that I have obtained private key file SSHkey-bba1.pem 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.

(Optional) Advanced Configuration

Table 5 MRS cluster advanced configuration




For details, see Managing Cluster Tags.

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 Auto Scaling Rules When Creating a Cluster. If the cluster billing mode is Yearly/Monthly, auto scaling can be configured only after you specify Task node specifications and set Instance Count of the Task node to 0.

Bootstrap Action

For details, see Adding a Bootstrap Action.


An agency allows ECS or BMS to manage MRS resources. You can configure an agency of the ECS type to automatically obtain the AK/SK to access OBS. For details, see Accessing OBS Using an ECS Agency.

Big Data Job

For details, see Running a MapReduce Job.

OBS Permission Control

Users who have enabled fine-grained permission control can use this function to grant permissions on different directories in OBS buckets to different MRS users. For details, see Configuring Fine-Grained Permissions for MRS Multi-User Access to OBS.

Metric Sharing

Monitoring metrics of big data components are collected. If a fault occurs when you use a cluster, share the monitoring metrics with HUAWEI CLOUD technical support personnel for troubleshooting.

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.

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. For details, see EVS Disk Encryption.

Data Disk 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.

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.

Data Disk 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.

Failed to Create a Cluster

If a cluster fails to be created, the failed task will be managed on the Failed Tasks page. Click shown in Figure 1 to go to the Failed Tasks page. In the Status column, hover the cursor over to view the failure cause. See Figure 2. You can delete failed tasks by referring to Deleting a Failed Task.

Figure 1 Failed task management
Figure 2 Failure cause

Table 6 lists the error codes of MRS cluster creation failures.

Table 6 Error codes

Error Code



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


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


Invalid request. Try again later or contact customer service.


Insufficient resources. Try again later or contact customer service.


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


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


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


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


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

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?

Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel