This topic describes the common configuration parameters in AnalyticDB for MySQL.
Configuration | Parameter | Description | Example | References |
Switchover window | REPLICATION_SWITCH_TIME_RANGE | The window during which the existing cluster is switched over to a new cluster. During a switchover to a new cluster, the existing cluster becomes read-only for a period of 5 to 10 minutes. After you are connected to the existing cluster, you can set the REPLICATION_SWITCH_TIME_RANGE parameter to specify the switchover window. Note If the switchover window is not specified, the existing cluster is switched over to a new cluster after the incremental data of the existing cluster is synchronized in real time to the new cluster. |
| Scale a Data Warehouse Edition cluster and change the cluster mode |
Maximum number of values specified by the IN operator | MAX_IN_ITEMS_COUNT | The maximum number of values that can be specified by the IN operator. Default value: 2000. |
| |
Query timeout period | QUERY_TIMEOUT | The timeout period of all queries in a cluster. Unit: milliseconds. |
| |
The timeout period of a single query. Unit: milliseconds. |
| |||
Timeout period of INSERT, UPDATE, and DELETE statements | INSERT_SELECT_TIMEOUT | The maximum execution duration of the INSERT, UPDATE, and DELETE statements in a cluster. Default value: 24 × 3600000. Unit: milliseconds. |
| |
The maximum execution duration of the INSERT, UPDATE, and DELETE statements in a query. Default value: 24 × 3600000. Unit: milliseconds. |
| |||
Filter conditions without pushdown |
| Disables filter condition pushdown for specific columns in a cluster. |
| |
Disables filter condition pushdown for specific columns in a query. |
| |||
Query execution mode | QUERY_TYPE | The query execution mode of a cluster. Valid values:
Note The query execution mode of a Data Warehouse Edition (V3.0) cluster in reserved mode or a Data Lakehouse Edition (V3.0) cluster cannot be changed. |
| |
Query queue | XIHE_ENV_QUERY_ETL_MAX_CONCURRENT_SIZE | The maximum number of queries that can be executed for LOWEST queues on a single frontend node. Default value: 20. |
| Priority queues and concurrency control of interactive resource groups |
XIHE_ENV_QUERY_ETL_MAX_QUEUED_SIZE | The maximum number of queries that can be queued for LOWEST queues on a single frontend node. Default value: 200. |
| ||
XIHE_ENV_QUERY_LOW_PRIORITY_MAX_CONCURRENT_SIZE | The maximum number of queries that can be executed for LOW queues on a single frontend node. Default value: 20. |
| ||
XIHE_ENV_QUERY_LOW_PRIORITY_MAX_QUEUED_SIZE | The maximum number of queries that can be queued for LOW queues on a single frontend node. Default value: 200. |
| ||
XIHE_ENV_QUERY_NORMAL_MAX_CONCURRENT_SIZE | The maximum number of queries that can be executed for NORMAL queues on a single frontend node. Default value: 20. |
| ||
XIHE_ENV_QUERY_NORMAL_MAX_QUEUED_SIZE | The maximum number of queries that can be queued for NORMAL queues on a single frontend node. Default value: 200. |
| ||
XIHE_ENV_QUERY_HIGH_MAX_CONCURRENT_SIZE | The maximum number of queries that can be executed for HIGH queues on a single frontend node. Default value: 40. |
| ||
XIHE_ENV_QUERY_HIGH_MAX_QUEUED_SIZE | The maximum number of queries that can be queued for HIGH queues on a single frontend node. Default value: 400. |
| ||
Data import by using MaxCompute external tables | SQL_OUTPUT_BATCH_SIZE | The amount of batch imported data. |
| |
ENABLE_ODPS_MULTI_PARTITION_PART_MATCH | Specifies whether to obtain the number of entries in each MaxCompute partition in advance. |
| ||
Automatic scheduling for BUILD jobs | RC_CSTORE_BUILD_SCHEDULE_PERIOD | The time range within which you want to schedule BUILD jobs. This parameter applies to job scheduling, not job execution. The values of start_time and end_time must be integers. Valid values: 0 to 24. |
| |
Scheduling priority of BUILD jobs | build_task_priority | Configures a scheduling priority for only one table. The configured priority takes effect only for the current BUILD job. The |
| |
ADB_CONFIG RC_BUILD_TASK_PRIORITY_LIST | Configures scheduling priorities for one or more tables. The configured priorities are effective until you configure new scheduling priorities of BUILD jobs for the tables. The |
| ||
Elastic import | RC_ELASTIC_JOB_SCHEDULER_ENABLE | Enables the elastic import feature. |
| |
| Selects elastic import and configures a resource group for the import job. |
|