Buying a Custom Cluster
To use MRS, buy a cluster on 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 an account. For details, see Creating an MRS User.
Video Tutorial
This tutorial demonstrates how to create an MRS 3.1.0 cluster on the management console and configure software, hardware, and advanced settings.
The UI may vary depending on the version. This tutorial is for reference only.
Procedure
- Go to the Buy Cluster page.
- Click the Custom Config tab.
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.
- Configure cluster information by referring to Software Configurations and click Next.
Figure 1 Configure Software
Only one billing mode is supported in some regions. For details, see the management console.
- Configure cluster information by referring to Hardware Configurations and click Next.
Figure 2 Configure Hardware
To add a task node group in the current MRS cluster for auto scaling, perform the following operations:
Add an analysis task node group.- For a cluster whose Cluster Type is Analysis cluster or Hybrid cluster:
The system automatically adds the analysis task node group task_node_analysis_group. Set the number of nodes, instance specifications, and node disk configurations as needed.
If the analysis task node group is not required, you can manually delete it.
- For a cluster whose Cluster Type is Custom:
- In the cluster node configuration area, click Add Node Group to manually add a node group.
- Set Topology Adjustment to Enable.
- Manually select the role topology so that the node group contains only the NodeManager (NM) role.
You can also manually add a task node group after the cluster is created. For details, see Adding a Task Node.
Add a streaming task node group (supported only by MRS 1.9.2):
For a cluster whose Cluster Type is Streaming cluster or Hybrid cluster:
The system automatically adds the streaming task node group task_node_streaming_group. Set the number of nodes, instance specifications, and node disk configurations as needed.
If the streaming task node group is not required, you can manually delete it.
- For a cluster whose Cluster Type is Analysis cluster or Hybrid cluster:
- Set advanced options by referring to Advanced Options Then, click Next.
Figure 3 Set Advanced Options
- On the Confirm Configuration page, check the cluster configuration information. If you need to adjust the configuration, click to go to the corresponding tab page and configure parameters again.
- Select the checkbox to enable secure communications. For details, see Communication Security Authorization.
- Click Buy Now.
If Kerberos authentication is enabled, check whether this function is required. If it is, click Continue. If not, click Back to disable it and then proceed with the subsequent step. This option cannot be changed after you buy a cluster.
For any doubt about the pricing, click Pricing details in the lower left corner.
If you select the pay-per-use billing mode, the order may fail to be placed because the account may be in risk. In this case, contact technical support.
- 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 Configurations
Parameter |
Description |
---|---|
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. |
Billing Mode |
MRS provides two billing modes.
|
Required Duration |
This parameter is valid in Yearly/Monthly billing mode and indicates a cluster subscription duration. The minimum cluster duration is 1 month and the maximum available cluster duration is 1 year. If Auto-renew is selected, monthly subscriptions are automatically renewed every month and yearly subscriptions are automatically renewed every year. |
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 Type |
The cluster types are as follows:
NOTE:
|
Version Type |
The following version types are available:
The default version type is Normal. |
Cluster Version |
Currently, MRS 1.9.2, 3.1.0, 3.1.5, 3.2.0-LTS.1, and 3.1.2-LTS.3, and are supported. The latest version of MRS is used by default. |
Component |
MRS cluster components. For details about component versions supported by different versions of MRS clusters, see List of MRS Component Versions. |
Metadata |
Whether to use external data sources to store metadata.
Clusters that support the Hive or Ranger component support this function. |
Component |
This parameter is available only when Metadata is set to External data connection. It indicates the type of an external data source.
|
Data Connection Type |
This parameter is available only when Metadata is set to External data connection. It indicates the type of an external data source. When you create a cluster, Data Connection Type can only be set to Local database. |
Component port (supported only for the LTS version) |
Policy of the default communication port of each component in the MRS cluster.
For details about the differences between default open source port and default custom port, see Web UIs of Open Source Components. |
Hardware Configurations
Parameter |
Description |
---|---|
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. |
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. |
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?
NOTE:
The number of IP addresses required by creating an MRS cluster depends on the number of cluster nodes and selected components, but not the cluster type. In MRS, IP addresses are automatically assigned to clusters during cluster creation basically based on the following formula: Quantity of IP addresses = Number of cluster nodes + 2 (one for Manager; one for the DB). In addition, if the Hadoop, Hue, Sqoop, and Presto or Loader and Presto components are selected during cluster deployment, one IP address is added for each component. To buy a ClickHouse cluster independently, the number of IP addresses required is calculated as follows: Number of IP addresses = Number of cluster nodes + 1 (for Manager). |
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.
NOTE:
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 0.0.0.0/0 as a source address. Otherwise, security risks may occur. If you do not know the trusted accessible IP address range, select Auto create. |
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 buy one.
NOTE:
The EIP must be in the same region as the cluster. |
Parameter |
Description |
---|---|
CPU Architecture |
CPU architecture supported by MRS. This parameter is not available for MRS 3.1.0 and 3.1.5.
|
Common Node Configurations |
This parameter is available only when Cluster Type is set to Custom. Value options include Compact, Full-size, and OMS-separate. For details, see Custom Cluster Template Description. |
Node Group |
Name of a node group An MRS cluster consists of multiple ECS nodes. The system manages the nodes based on node groups. Nodes in a cluster are classified into the following types based on the roles of components deployed on the nodes:
|
Node Type |
Type of the nodes in the group. Options include Core and Task.
NOTE:
If the node group type is set to Task, only the NodeManager role (except mandatory roles) can be deployed in the node group. |
Payment Type |
Billing mode of nodes in a cluster.
|
Node Count |
Configure node quantity in each node group.
NOTE:
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. |
Instance Specifications |
Instance specifications of Master or Core nodes. MRS supports host specifications determined by CPU, memory, and disk space. See ECS Specifications Used by MRS and to obtain the allowed instance specifications. Click to configure the instance specifications, system disk, and data disk parameters of the cluster node. 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:
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.
NOTE:
|
System Disk |
Storage type and storage space of the system disk on a node.
Storage type can be any of the following:
|
Data Disk |
Data disk storage space of a node. For more data storage, you can add disks when creating a cluster. A maximum of 10 disks can be added to each Core or Task node.
The storage type can be any of the following:
NOTE:
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. |
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. |
Advanced Options
Parameter |
Description |
---|---|
Kerberos Authentication |
Whether to enable Kerberos authentication when logging in to Manager. This option cannot be changed after you buy a cluster.
|
Username |
Name of the administrator of Manager. admin is used by default. |
Password |
Password of the Manager administrator The following requirements must be met:
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 |
|
Hostname Prefix |
Enter the prefix for the computer hostname of an ECS or BMS in the cluster. |
Setting Advanced Options |
Advanced function parameters of an MRS cluster. Select Configure. For details, see Table 5. |
Parameter |
Description |
---|---|
Tag |
For details, see Adding a Tag to a Cluster/Node. |
Auto Scaling |
Auto scaling can be configured only after you specify task node specifications in the Configure Hardware step by referring to Configuring Auto Scaling Rules. |
Bootstrap Action |
For details, see Adding a Bootstrap Action. |
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. |
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 for MRS 3.1.0 and MRS 3.1.2-LTS.3. 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 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 for MRS 3.1.0 and MRS 3.1.2-LTS.3. |
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. This parameter is not available for MRS 3.1.0 and MRS 3.1.2-LTS.3. 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. |
Logging |
Whether to collect logs when cluster creation fails. After the logging function is enabled, system logs and component run logs are automatically collected and saved to the OBS file system in scenarios such as cluster creation failures and scale-out or scale-in failures for O&M personnel to quickly locate faults. The log information is retained for a maximum of seven days. |
Failed to Create a Cluster
If a cluster fails to be created, the failed task will be managed on the Manage Failed Tasks page. Choose Active Clusters. Click in Figure 4 to go to the Manage Failed Tasks page. In the Task Status column, hover your cursor over to view the failure cause. See Figure 5. You can delete failed tasks by referring to Viewing Failed MRS Tasks.
Table 6 lists the error codes of MRS cluster creation failures.
Error Code |
Description |
---|---|
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. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot