All Products
Search
Document Center

E-MapReduce:Create a StarRocks cluster

Last Updated:Jul 14, 2026

This topic describes how to create a StarRocks cluster.

Prerequisites

You have created a VPC and a vSwitch in the target region. For more information, see Create and manage a VPC and Create and manage a vSwitch.

Procedure

  1. Go to the cluster creation page.

    1. Log on to the E-MapReduce console.

    2. Optional: In the top navigation bar, select a region and, optionally, a resource group.

      • Region: The cluster is created in the selected region. This setting cannot be changed after creation.

      • Resource group: By default, all resources within your account are displayed.

    3. At the top of the page, click CREATE_CLUSTER.

  2. Configure the cluster.

    Configure the cluster's software, hardware, and basic settings.

    Important

    After a cluster is created, you can only change its name. Ensure all other configurations are correct before proceeding.

    1. Configure software settings.

      Parameter

      Example

      Description

      Region

      China (Hangzhou)

      The region where the cluster will be created. This setting cannot be changed after creation.

      Business Scenario

      Data Analytics

      Select Data Analytics.

      Product Version

      EMR-5.19.0

      The E-MapReduce version. The latest version is selected by default.

      High Service Availability

      Off

      When enabled, the cluster uses three master nodes to provide high availability for ResourceManager and NameNode. You can adjust the number of nodes.

      Optional Services

      StarRocks 3

      Select additional components based on your needs. For selected components, the related service processes start by default.

      Collect Service Operational Logs

      On

      Enabled by default, this feature collects operational logs from all services for diagnostic purposes.

      After the cluster is created, you can change the Collection Status of Service Operational Logs on the Basic Information page.

      Important

      If you disable log collection, health checks and technical support for E-MapReduce are limited, without affecting other features. For more information about how to disable this feature and its effects, see How do I stop collecting service logs?.

      StarRocks Architecture

      Shared-nothing

      This setting is available only for StarRocks 3.x.

      StarRocks supports both shared-nothing and shared-data architectures.

      • Shared-nothing (Default): Compute and storage resources are tightly coupled, and data is stored directly on the local disks of compute nodes.

        This architecture is suitable for Online Analytical Processing (OLAP) scenarios that require real-time processing and fast queries, such as data analytics and Business Intelligence (BI) report generation.

      • Shared-data architecture : Compute and storage resources are fully decoupled. Compute nodes focus on executing query tasks, while data is stored in an external distributed storage system. This improves system flexibility and reliability.

        This architecture is suitable for use cases that involve large-scale data storage and require elastic computing.

      DLF Unified Metadata

      Selected

      Selected by default. When selected, metadata is stored in Data Lake Formation (DLF).

      After you activate DLF, the system selects a default DLF Catalog for you, which is your user ID (UID). If you want to use different data catalogs for different clusters, create a new catalog:

      1. Click Create Catalog. In the dialog box that appears, enter a catalog ID and click OK.

      2. From the DLF Catalog drop-down list, select the catalog you created.

      Advanced Settings

      Off

      Custom Software Configuration: Allows you to specify a JSON file to configure underlying software such as Hadoop, Spark, and Hive. This feature is disabled by default.

    2. Configure hardware settings.

      Parameter

      Example

      Description

      Billing Method

      pay-as-you-go

      The following billing methods are supported:

      • Pay-as-you-go: A post-paid billing method where you pay for resources after using them. You are billed hourly for your actual usage. This method is ideal for short-term testing or dynamic tasks.

      • Subscription: A pre-paid billing method where you pay for resources before using them.

        Note

        We recommend using the Pay-as-you-go method for testing. After your tests are successful, create a new Subscription cluster for production use.

      Zone

      China (Hangzhou) Zone I

      Zones are separate physical locations within a region, connected by a low-latency internal network. In most cases, you can use the default zone.

      VPC

      starrocks_test/vpc-bp1f4epmkvncimpgs****

      An existing VPC is selected by default.

      To create a new VPC, go to the VPC console. For more information, see Create and manage a VPC.

      vSwitch

      vsw_test/vsw-bp1e2f5fhaplp0g6p****

      Select a vSwitch in the selected zone and VPC. If no vSwitch is available in the zone, go to the VPC console to create one. For more information, see VPCs and vSwitches.

      Default Security Group

      sg-bp1ddw7sm2risw****/sg-bp1ddw7sm2risw****

      An existing security group is selected by default. For more information about security groups, see Security group overview.

      You can also click create a new security group. to create a security group in the ECS console. For more information, see Create a security group.

      Important

      Do not use advanced security groups created in the ECS console.

      Node Group

      Use default values

      You can select instance types based on your requirements. For more information, see Instance families.

      • Master: Runs control plane services such as ResourceManager and NameNode.

      • Core: Stores data in the cluster's distributed file system (HDFS). You can also scale out Core nodes on demand after the cluster is created.

      • Task: Provides additional compute capacity and does not store data. This node group is optional and can be added to scale computing resources.

        Important

        Task node groups support pay-as-you-go, preemptible instance, and subscription billing methods.

      • Add to Deployment Set: When high availability is enabled, Master nodes are added to a deployment set by default. A deployment set is a policy that controls the distribution of instances. For more information, see Deployment sets.

      • System Disk: Select a standard SSD, enhanced SSD (ESSD), or ultra disk as needed. Adjust the system disk size as required.

      • Data Disk: Select a standard SSD, enhanced SSD (ESSD), or ultra disk as needed. Adjust the data disk size as required.

        Note

        When you select an enhanced SSD (ESSD), you can set different performance levels (PLs) based on the disk capacity to meet various cluster performance needs. The default performance level is PL1. Depending on the disk capacity, system disks support PL0, PL1, and PL2, while data disks support PL0, PL1, PL2, and PL3. For more information about cloud disks, see Cloud disk overview.

      • Instances: The Master node group has one instance by default. If high availability is enabled, you can have multiple Master instances.

        The Core node group has two instances by default. You can adjust this number as needed.

      • Additional Security Group: Additional security groups allow flexible access control between different external resources or applications. You can associate up to two additional security groups with this node group.

      • Assign Public Network IP: Specifies whether to assign an Elastic IP (EIP) address to the cluster. This is disabled by default. Only DataLake clusters support assigning public IPs at the node group level.

        Note

        If you do not enable this feature but want to use a public IP address to access the cluster after it is created, you must apply for one on the ECS console. For more information, see Apply for an EIP.

    3. Configure basic settings.

      In the Basic Information section, configure the following parameters.

      Parameter

      Example

      Description

      Cluster Name

      Emr-StarRocks

      The name of the cluster. The name must be 1 to 64 characters in length and can contain only Chinese characters, letters, digits, hyphens (-), and underscores (_).

      Identity Credentials

      Password

      Key Pair (Default): Uses an SSH key pair to log on to the master node.

      For more information about key pairs, see SSH key pairs.

      Password: Sets the logon password for the master node. The password must be 8 to 30 characters in length and contain uppercase letters, lowercase letters, digits, and special characters.

      Special characters include: ! @ # $ % ^ & *.

      Special characters include the exclamation point (!), at sign (@), number sign (#), dollar sign ($), percent sign (%), caret (^), ampersand (&), and asterisk (*).

      Advanced settings (optional)

      Parameter

      Description

      ECS Application Role

      When your program runs on an EMR compute node, you do not need to specify an Alibaba Cloud AccessKey to access related cloud services such as OSS. EMR automatically obtains a temporary AccessKey for the access, and the permissions of this key are controlled by an ECS Application Role.

      Bootstrap Actions

      Scripts that run on cluster nodes before services start. Use them to install software or customize the environment. For more information, see Run scripts by using bootstrap actions.

      Release Protection

      This feature prevents accidental deletion of pay-as-you-go clusters. If enabled, you must disable it before you can release the cluster. For more information, see Enable and disable release protection.

      Tags

      You can add tags when creating a cluster or after it is created. Tags help you identify and manage your cluster resources. For more information, see Manage tags.

      Resource Group

      Resource groups allow you to group your cloud resources by purpose, permissions, or ownership. For more information, see Use resource groups.

      Data Disk Encryption

      This feature can be enabled only when you create a cluster. When enabled, data at rest on the data disk is encrypted. For more information, see Enable data disk encryption.

      System Disk Encryption

      This feature can be enabled only when you create a cluster. When enabled, the operating system, program files, and other data at rest on the system disk are encrypted. For more information, see Enable system disk encryption.

      Remarks

      Used to record important information about the cluster. You can add or modify remarks on the Basic Information page after the cluster is created.

  3. (Optional) Save as Cluster Template: If you select Key Pair for logon credentials, you can click Save as Cluster Template to save the current cluster configuration as a cluster template.

    1. In the Save as Cluster Template dialog box, enter a Cluster Template Name and select a Cluster Template Resource Group.

      Parameter

      Description

      Cluster Template Name

      Enter a name for the cluster template to facilitate management. The name must be 1 to 64 characters long and can contain only Chinese characters, letters, digits, hyphens (-), and underscores (_).

      Cluster Template Resource Group

      Select an existing resource group to organize your templates.

      If you need to create a new resource group, you can click Create Resource Group. below. For more information, see Create a resource group.

    2. Click OK.

      A new cluster template is added to the Manage Cluster Templates panel. For more information about cluster templates, see Create a cluster template.

  4. Click Confirm.

    Refresh the page to view the creation progress. The cluster is ready when its Status changes to Running.

FAQ

What is the relationship between master nodes, core nodes, and the frontend (FE) and backend (BE) nodes of StarRocks?

The StarRocks Frontend (FE) is deployed on master nodes. By default, a single node is used. In high-availability mode, the deployment defaults to three nodes, and an FE process is deployed on each master node. Enabling the High Service Availability switch creates a high-availability cluster that provides fault tolerance and load balancing.

StarRocks backend nodes (BE) are deployed on the E-MapReduce core nodes. Each core node runs one BE process. Select the number of core nodes based on your business needs.