All Products
Search
Document Center

Lindorm:Activation and Management

Last Updated:Mar 28, 2026

OLAP resource groups are computing resource units for the Lindorm compute engine. Each resource group provides a MySQL-compatible access interface and handles high-concurrency, low-latency analytical queries. Multiple resource groups can coexist in the same instance, each with independent compute but sharing the same underlying storage — so deleting a resource group releases only its compute resources and does not affect stored data.

Prerequisites

Before you begin, ensure that you have:

Resource group lifecycle

A resource group moves through the following states:

StateDescription
StartingResource group is being provisioned after creation or restart
RunningResource group is active and accepting queries
RestartingResource group is applying a configuration change
FailedProvisioning failed due to insufficient resources or IP addresses

If a resource group stays in Failed after repeated creation attempts, contact Lindorm technical support (DingTalk ID: s0s3eg3).

When you activate the compute engine, an extract, transform, and load (ETL) resource group named <code class="inline-code___exakR" data-tag="code" id="cab90be41a76r">default</code> is automatically created. This resource group only supports property configuration changes — it cannot be deleted or restarted.

Create an OLAP resource group

  1. Log on to the Lindorm console. In the upper-left corner, select the region of your instance. On the Instances page, click the instance ID or click View Instance Details in the Actions column.

  2. On the Instance Details page, in the Configurations section, click Resource Groups in the Actions column for Compute Engine.

  3. On the Resource Group Details page, click Create Resource Group and set the following parameters:

    ParameterDescription
    Resource Group TypeSelect OLAP
    Resource Group NameUp to 63 characters; lowercase letters and digits only. Example: cg0
    Node SpecificationsSelect the node specification that fits your workload
    Working Nodes in Job (WORKERS)Number of worker nodes for query execution. Integer from 4–1,024; default is 4. More workers improve concurrent query throughput but increase resource consumption
  4. Click OK. The resource group takes about 20 minutes to provision. Once its status changes to Running, connect to it and access data.

Get the web UI address

The web UI shows system information and lets you monitor resource group status.

  1. On the Resource Group Details page, hover over WebUI in the Actions column.

  2. Copy the web UI address that appears. Example: http://alb-57k7r581oht8rd****.cn-hangzhou.alb.aliyuncsslb.com/computegroup/cg0

Edit resource group configuration

You can change the node specifications and worker node count after creating an OLAP resource group.

The changes only take effect after you restart the resource group.

  1. On the Resource Group Details page, click Edit in the Actions column.

  2. On the Update Resource Group page, select the new Node Specifications and Working Nodes in Job.

  3. Click OK to save the configuration.

After saving, restart the resource group to apply the changes.

Restart the resource group

Restarting a resource group releases its existing compute resources and recreates it with the saved configuration.

Warning

During a restart, all connections to the resource group are dropped and all in-flight queries fail. The resource group is unavailable until the restart completes and the status returns to Running.

  1. On the Resource Group Details page, click Restart in the Actions column.

  2. Click OK to confirm.

Delete a resource group

  1. On the Resource Group Details page, click image in the Actions column.

  2. In the confirmation dialog, click Delete.

  3. Click OK.

Deleting a resource group releases only its compute resources. Data in the shared storage layer is not affected.

Set the default resource group

When you use the SQL endpoint of the compute engine, queries are automatically routed to the default resource group. Setting a default resource group prevents query failures caused by an unspecified target.

The system applies these rules automatically:

  • The first OLAP resource group you create becomes the default.

  • If you delete the current default, the system randomly selects another OLAP resource group in the instance as the new default.

To manually change the default, toggle the switch in the Default Resource Group column on the Resource Group Details page.

Only one default resource group can be active at a time. Setting a new default automatically unsets the previous one.

What's next