All Products
Search
Document Center

ApsaraDB for SelectDB:Configure parameters

Last Updated:Mar 13, 2025

ApsaraDB for SelectDB provides various parameters that can be used to configure different features, such as log retention, feature disabling, and access control. This topic describes how to configure the parameters based on your business requirements and view the change history of the parameters. This helps ensure optimal business effects and database performance.

Prerequisites

  • Your ApsaraDB for SelectDB instance runs a kernel version of 2.4 or later.

  • The cluster that you want to manage is in the Running state.

Impacts

If Yes is displayed in the Force Restart column of the parameter that you want to modify, the cluster is restarted for the modification to take effect.

  • If you modify the parameters of a frontend (FE) cluster or a backend (BE) cluster, the FE cluster or the BE cluster is restarted for the modification to take effect.

  • Rolling restart: Nodes in the cluster are restarted in sequence. In this case, the cluster is still available, but transient connections occur.

  • Parallel restart: Nodes in the cluster are restarted at the same time. In this case, the cluster becomes unavailable for 1 to 5 minutes. We recommend that you perform the parallel restart during off-peak hours.

Modify parameters

  1. Log on to the ApsaraDB for SelectDB console.

  2. In the top navigation bar, select the region in which the instance that you want to manage resides.

  3. In the left-side navigation pane, click Instances. On the page that appears, find the required instance and click the instance ID.

  4. In the left-side pane of the page that appears, click Parameters.

  5. On the Parameter Settings tab, select a cluster whose parameters you want to modify from the Select Cluster drop-down list.

  6. Find the parameter that you want to modify and click the image icon in the Current Value column to modify the parameter. You can enter a value in the New Value field based on the valid values and click OK.

    • Optional. In the upper-left corner of the page, turn on Show Modified Parameters Only to view the parameters that are modified but not submitted.

    • Optional. In the upper-left corner of the page, click Undo Current Modification to cancel the modifications to the parameters that are modified but not submitted.

  7. After you modify the parameters, click Apply Changes in the upper-right corner. In the Save Settings dialog box, configure the following parameters.

    Parameter

    Description

    Select Modification Time

    The time when you want the modification to take effect. Valid values:

    • Modify Now: The modification immediately takes effect.

    • Modify Within Maintenance Window: The modification takes effect within the maintenance window that you specify. For more information, see Specify a maintenance window.

      Important

      If Yes is displayed in the Force Restart column of the parameter that you modified, the cluster is restarted for the modification to take effect. We recommend that you set the Select Modification Time parameter to Modify Within Maintenance Window in the Save Settings dialog box. This reduces the impact of the cluster restart on your workloads.

    Parallel Operation Node

    Specifies whether to perform the parallel restart on nodes. By default, the rolling restart is used.

    Note

    The cluster needs to be restarted only when Yes is displayed in the Force Restart column.

    • If you do not select Parallel Operation Node, the rolling restart is used. You must take note of the following items:

      The nodes in a cluster of an instance are modified in sequence. In this case, the cluster is still available, but transient connections occur. We recommend that you use the rolling restart.

    • If you select Parallel Operation Node, the parallel restart is used. You must take note of the following items:

      The nodes in a cluster of an instance are modified and restarted at the same time. In this case, the cluster becomes unavailable for 1 to 5 minutes. If you want to restart a cluster in a quick manner, you can use the parallel restart.

  8. Click OK.

    Note

    After you submit the modification, the modification does not immediately take effect. You can go to the Modification History tab and check whether the modification takes effect based on the value in the Take Effect column.

View the parameter modification history

  1. Log on to the ApsaraDB for SelectDB console.

  2. In the top navigation bar, select the region in which the instance that you want to manage resides.

  3. In the left-side navigation pane, click Instances. On the page that appears, find the required instance and click the instance ID.

  4. In the left-side pane of the page that appears, click Parameters.

  5. On the Modification History tab, select the cluster whose parameter modification history you want to view from the Select Cluster drop-down list.