When multiple teams or workflows share the same Lindorm compute engine, resource contention can cause latency spikes and unpredictable job failures. ETL resource groups let you partition compute resources so that each team or workflow gets a dedicated allocation. With resource groups, you can:
-
Assign dedicated CPU, memory, and daily compute quotas to specific teams or workflows
-
Choose between serverless elastic compute (resources scale on demand) and resident compute (resources stay allocated)
-
Control which users can submit jobs to each resource group
-
Delete or reconfigure groups as your workload changes
Prerequisites
Before you begin, ensure that you have:
-
An activated LindormTable instance
-
An activated Lindorm compute engine
Choose a resource group type
ETL resource groups support two types. Choose based on your workload characteristics:
| Not resident (serverless) | Resident | |
|---|---|---|
| How resources work | Requested on demand, released after the job ends | Allocated upfront and kept running |
| Best for | Intermittent or unpredictable workloads | Steady, latency-sensitive workloads |
| Key parameters | Daily quota (CU-hours), CPU core limit, memory limit, authorized users | Node specifications, number of worker nodes |
CU-hours (CUH): one compute unit (CU) running for one hour.
Create an ETL resource group
-
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.
-
On the Instance Details page, in the Configurations section, click Resource Groups in the Actions column for Compute Engine.
-
On the Resource Group Details page, click Create Resource Group.
-
Set Resource Group Type to ETL.
-
In the Resource Group Name field, enter a name. The name can contain only lowercase letters and digits, and can be up to 63 characters long. For example:
etlcg0. -
Set Whether resident and configure the parameters for your chosen type:
Not resident:
Parameter Description Daily Resource Quota Maximum resources consumable per day, in CU-hours (CUH). Valid range: 0–100,000. A value of 0 means no limit. When the daily limit is reached, no additional jobs can be submitted that day. Maximum number of CPU cores Maximum CPU cores available in the group. Minimum value: 100. When running jobs exceed this limit, no additional jobs can be submitted. Maximum memory size Maximum memory available in the group, in GB. Minimum value: 400 GB. When running jobs exceed this limit, no additional jobs can be submitted. Authorize Users Users who can submit jobs to this resource group. Enter *to allow all users.Resident:
Parameter Description Node Specifications Specifications of the worker nodes in the Spark cluster. Working Nodes in Job Number of worker nodes in the Spark cluster. -
Click OK.
Submit a job to a specific ETL resource group
To route a job to a specific resource group, add the compute-group parameter to the job configuration:
compute-group=${ETLComputeGroupName}
Replace ${ETLComputeGroupName} with the name of your resource group.
Edit a resource group
After creating an ETL resource group, you can update its daily resource quota, CPU limit, memory limit, and authorized users.
-
On the Resource Group Details page, click Edit in the Actions column.
-
On the Update Resource Group page, modify the settings as needed.
-
Click OK.
Access an ETL resource group from Alibaba Cloud DataWorks
DataWorks is a one-stop platform for intelligent big data development and administration. Use it to submit Spark or Spark SQL tasks to the Lindorm compute engine and orchestrate workflows for offline task scheduling. For details, see:
Delete a resource group
Deleting a resource group is irreversible. After deletion, no jobs can be submitted to it. Before you delete, go to Compute Engine > Instance Monitoring in the instance console to confirm no jobs are currently running in the resource group.
To delete the resource group:
-
On the Resource Group Details page, click
in the Actions column. -
In the confirmation dialog, click Delete.
-
Click OK.