Parameter configuration

ApsaraDB for SelectDB provides configurable parameters for log retention, feature disablement, and security control. You can configure and view these parameters to optimize workload and database performance.

Prerequisites

The ApsaraDB for SelectDB instance runs kernel version 2.4 or later.
The target cluster is in the Running state.

Impact

If the Force Restart column for a modified parameter is set to Yes, the cluster restarts.

Modifying parameters for an FE or BE cluster restarts only that cluster.
rolling restart: Nodes restart one by one. The cluster remains available, but transient connection interruptions may occur.
parallel restart: All nodes restart at the same time, making the cluster unavailable for 1 to 5 minutes. We recommend performing this operation during off-peak hours.

Modify parameters

Log on to the ApsaraDB for SelectDB console.
In the top-left corner of the page, select the region of your instance.
On the Instances page, click the target Instance ID to go to the Instance Details page.
In the left navigation bar, click Parameters.
On the Parameters page, select the Parameter Settings tab, and in the Select Cluster drop-down list, select the cluster whose parameters you want to modify.
Click the Edit icon in the Current Value column, enter a parameter value based on the suggested Input Range, and click OK.
- Optional: Click Show Modified Parameters Only in the upper-left corner of the page to view the parameters that you have modified but not submitted.
- (Optional) Click Undo Current Modification in the upper-right corner of the page to discard any changes that you have made but not yet submitted.

After you modify all parameters, click Apply Changes in the upper-right corner of the page. In the Save Settings dialog box that appears, configure the parameters as prompted:

Parameter

Description

Modification time

ApsaraDB for SelectDB instances support the following modification schedules:

Modify Now: The instance applies the changes immediately.
Modify Within Maintenance Window: The instance applies the changes during 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 modified parameter is Yes, the cluster will restart. We strongly recommend that you set Modification Time to Modify during Maintenance Window to reduce the impact of the cluster restart on your services.

Parallel operation

Specifies whether to perform a parallel restart. By default, a rolling restart is performed.

Note

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

If you do not select Parallel operation, a rolling restart is performed. Nodes restart one by one. The cluster remains available, though transient connection interruptions may occur. This method is recommended.
If you select Parallel operation, a parallel restart is performed. All nodes restart at the same time, making the cluster unavailable for 1 to 5 minutes. Select this option for a faster restart.

Click OK.

Note
Parameter changes do not take effect immediately after submission. On the Modification History tab, check the Take Effect column for the corresponding Parameter Name to verify whether the change has taken effect.

View modification history

Log on to the ApsaraDB for SelectDB console.
In the top-left corner of the page, select the region of your instance.
On the Instances page, click the target Instance ID to go to the Instance Details page.
In the left navigation bar, click Parameters.
On the Parameters page, select the Modification History tab, and in the Select Cluster dropdown list, select the cluster whose parameter modifications you want to view.