Scenario-based parameters are preset collections of configuration settings that allow you to quickly optimize your ApsaraDB for SelectDB cluster for a specific workload. Applying these parameters simplifies configuration, improves query and write performance, and ensures configuration consistency across different clusters.

Preset scenario-based parameters

ApsaraDB for SelectDB provides three preset scenario-based parameter templates. The following table describes the use cases and optimization focus for each template.

Template name	Description
General Analysis Scenario	Use cases: The default configuration for various mixed workloads, such as interactive data analysis and reporting queries. This template balances performance and resource consumption. Optimization focus: Balanced query concurrency General-purpose memory and cache configurations Standard load balancing policies
Log Analysis Scenario	Use cases: Designed for storing and analyzing massive volumes of log data, with a focus on high-throughput writes and large-scale data scans. This template is ideal for write-heavy, read-light scenarios that involve batch data ingestion and infrequent, latency-insensitive queries. Optimization focus: Optimized batch import configurations Enhanced data compression strategies Query adjustments for large-scale data scans
High-Concurrency Point Query Scenario	Use cases: Optimized for a high volume of concurrent, precise queries (typically based on a primary key) that require millisecond-level responses. This template is ideal for read-heavy, write-light workloads with a QPS ranging from tens to hundreds of thousands, where query latency is critical. Optimization focus: High-concurrency query processing capability Enhanced in-memory caching to reduce latency Connection pool optimization for rapid response

Select a scenario for a new instance

On the ApsaraDB for SelectDB purchase page, select the appropriate Business Scenario.

Modify parameters for an existing instance

For an existing instance, you can modify its parameter configuration in two ways: apply a preset scenario-based template or reuse parameters from another cluster.

Apply or switch a scenario-based template

Use this method to quickly switch your cluster to a standard, optimized configuration template.

Log on to the ApsaraDB for SelectDB console.
In the upper-left corner of the page, select the region where your instance is located.
On the Instances page, click the target Instance ID to open the Instance Details page.
In the left-side navigation pane, click Parameters.
On the Parameters page, select the parameter settings tab and click Modify scene settings.
Select the scenario to which you want to switch, review the Scene transition impact, and then click Switch scene.
- The instance status changes to Modifying Parameters. After the modification is complete, the status changes to running.
- If the scenario-based parameters do not meet your needs, you can customize them. For more information, see Parameter configuration.

Reuse parameters from another cluster

Use this method to precisely copy the parameter configuration from one cluster to another to ensure environment consistency.

Important

Note the following limitations for reusing cluster parameters:

You can only copy parameters between BE clusters within the same instance.
Copying parameters between FE clusters or across cluster types (for example, from a BE to an FE cluster) is not supported.
This operation requires an available source cluster.

Log on to the ApsaraDB for SelectDB console.
In the upper-left corner of the page, select the region where your instance is located.
On the Instances page, click the target Instance ID to open the Instance Details page.
In the left-side navigation pane, click Parameters.
On the Parameters page, select the parameter settings tab and click Reuse parameters from another cluster.

In the Reuse parameters from another cluster dialog box, select the source cluster.
Click Next, review the Parameter comparison, and then click Next.

In the Confirm and submit dialog box, configure the following parameters as prompted:

Parameter

Description

modification time

ApsaraDB for SelectDB instances support the following modification methods:

Modify Now: The parameter changes are applied to the instance immediately.
Modify Within Maintenance Window: The parameter changes are applied during the maintenance window that you specify. For more information about how to set a maintenance window, see Set a maintenance window.

Important
If the Force Restart column for a parameter is Yes, the cluster will restart. We strongly recommend setting the modification time to Apply during maintenance window to minimize the impact of the cluster restart on your services.

parallel operation

Specifies whether to perform the operation on nodes in parallel. By default, the system uses a rolling operation.

Note

A restart occurs only if the Force Restart column for a modified parameter is Yes.

If you do not select Parallel operation nodes, a rolling operation is performed, which has the following features:

The system modifies and restarts nodes sequentially. This can cause brief connection interruptions, but the cluster remains available. This is the recommended method.
Selecting Parallel Operation Node configures a parallel operation, which has the following features:

All nodes are modified and restarted simultaneously, causing the cluster to be unavailable for one to five minutes. Choose this method if you need a faster restart.

Click Confirm and apply.

Note
After you submit parameter changes, the changes do not take effect immediately. On the Modification History tab, you can check the Take Effect column for the corresponding Parameter Name to confirm whether the parameters have taken effect.

Scenario-based parameter

Scenario-based parameters are collections of preset parameter configurations used to quickly optimize SelectDB clusters for specific workloads. Applying these parameters simplifies configuration, improves query and write performance, and ensures configuration consistency across different clusters.

Preset scenario-based parameters

SelectDB provides three preset templates for scenario-based parameters. The following table outlines the use cases and key optimizations for each template.

Template name	Use cases and key optimizations
General analysis scenario	Use cases: This is the default configuration for various mixed workloads, such as interactive data analysis and reporting queries. This template balances performance with resource consumption. Key optimizations: Balanced query concurrency General memory and cache settings Standard load balancing strategies
Log analysis scenario	Use cases: Designed for storing and analyzing massive log data, with a focus on high-throughput writes and large-scale data scans. This template is ideal for write-heavy, read-light workloads that use batch ingestion, have infrequent queries, and are not sensitive to latency. Key optimizations: Optimized batch import settings Enhanced data compression strategies Query adjustments for large-scale data scans
High-concurrency point query scenario	Use cases: Optimized for high concurrency of precise queries, usually based on a primary key, that require millisecond-level response times. This template is ideal for read-heavy, write-light workloads with a QPS of tens to hundreds of thousands, where query latency is critical. Key optimizations: High-concurrency query processing Enhanced memory caching to reduce latency Connection pool optimization for fast responses

Select a scenario for a new instance

On the ApsaraDB for SelectDB purchase page, select the business scenario.

Modify parameters for an existing instance

For existing instances, you can modify parameter settings in two ways: apply a preset scenario-based template or reuse parameter settings from another cluster.

Apply or switch a scenario-based template

This method is suitable for scenarios where you need to quickly switch the cluster configuration to a standard, optimized template.

Log on to the ApsaraDB for SelectDB console.
In the upper-left corner of the page, select the region where the instance is located.
On the Instances page, click the target Instance ID to go to the Instance Details page.
In the navigation pane on the left, click Parameters.
On the Parameters page, select the Parameter Settings tab and click Modify Scenario Settings.
Select the scenario to switch to, read the Scenario Switch Impact, and then click Switch Scenario.
- The instance status changes to Modifying Parameters. After the parameters are modified, the status changes to Running.
- If the scenario-based parameters do not meet your needs, you can adjust them manually. For more information, see Parameter settings.

Reuse parameters from another cluster

This method is suitable for scenarios where you need to precisely copy the parameter settings from one cluster to another to ensure a consistent environment.

Important

Reusing cluster parameters has the following limitations:

You can only copy parameters between BE clusters within the same instance.
You cannot copy parameters between FE clusters or across cluster types, such as from a BE cluster to an FE cluster.
An available source cluster must exist before you perform this operation.

Log on to the ApsaraDB for SelectDB console.
In the upper-left corner of the page, select the region where the instance is located.
On the Instances page, click the target Instance ID to go to the Instance Details page.
In the navigation pane on the left, click Parameters.
On the Parameters page, select the Parameter Settings tab and click Reuse other cluster parameters.
In the Reuse other cluster parameters dialog box, Select the source cluster.
Click Next step. Review the Parameter Comparison, and if everything is correct, click Next step.

In the Confirm reuse and submit dialog box, configure the parameters as prompted:

Parameter

Description

Select Modification Time:

ApsaraDB for SelectDB instances support the following modification methods:

Modify Now: The parameters of the instance are modified immediately.
Modify Within Maintenance Window: The parameters of the instance are modified within the specified maintenance window. For more information about how to set a maintenance window, see Set a maintenance window.

Important
If the Force Restart column for a parameter is set to Yes, the cluster will restart. We strongly recommend setting Select Modification Time: to Modify Within Maintenance Window to minimize the impact of the cluster restart on your business.

Parallel Operation Node

Specifies whether to perform operations on nodes in parallel. The default is a rolling operation.

Note

A restart occurs only if the Force Restart column for a modified parameter is set to Yes.

If you do not select Parallel Operation Node, a rolling operation is performed. This operation has the following characteristics:

Nodes are modified and restarted one by one. Connections may be briefly interrupted, but the cluster remains available. This method is recommended.
If you select Parallel Operation Node, a parallel operation is performed. This operation has the following characteristics:

Nodes are modified and restarted at the same time. This makes the cluster unavailable for 1 to 5 minutes. Select this method if you want the restart to complete more quickly.

Click Confirm reuse and submit for effect..

Note
After you submit the parameter changes, they do not take effect immediately. You can go to the Modification History tab and check the Take Effect column for the corresponding Parameter Name to confirm whether the changes have taken effect.