This topic describes the common configuration parameters in AnalyticDB for MySQL.

Configuration Parameter Description Example References
Switchover window REPLICATION_SWITCH_TIME_RANGE Specifies 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.
SET adb_config REPLICATION_SWITCH_TIME_RANGE=`23:00, 23:30`; Modify the configurations of a cluster
Maximum number of values specified by the IN operator MAX_IN_ITEMS_COUNT Specifies the maximum number of values that can be specified by the IN operator. Default value: 2000. SET adb_config MAX_IN_ITEMS_COUNT=3000; Development FAQ
Query timeout period QUERY_TIMEOUT Specifies the timeout period of all queries in a cluster. Unit: milliseconds. SET adb_config QUERY_TIMEOUT=1000;
Specifies the timeout period of a single query. Unit: milliseconds. /*+ QUERY_TIMEOUT=1000 */select count(*) from t;
Timeout period of INSERT, UPDATE, and DELETE statements INSERT_SELECT_TIMEOUT Specifies the maximum execution duration of the INSERT, UPDATE, and DELETE statements in a cluster. Default value: 24*3600000. Unit: milliseconds. SET adb_config INSERT_SELECT_TIMEOUT=3600000; Limits
Specifies the maximum execution duration of the INSERT, UPDATE, and DELETE statements in a query. Default value: 24*3600000. Unit: milliseconds. /*+ INSERT_SELECT_TIMEOUT=3600000 */update customer set customer_name ='adb' where customer_id ='2369';
Filter conditions without pushdown
  • Engine version 3.1.4 or later: FILTER_NOT_PUSHDOWN_COLUMNS
  • Engine version earlier than 3.1.4: NO_INDEX_COLUMNS
Disables filter condition pushdown for specific columns in a cluster.
  • Engine version 3.1.4 or later: SET adb_config FILTER_NOT_PUSHDOWN_COLUMNS=[${database}.${tableName}:${col1Name}|${col2Name}];
  • Engine version earlier than 3.1.4: set adb_config NO_INDEX_COLUMNS=[${tableName}.${col1Name};${col2Name},${tableName1}.${col1Name}]
Filter conditions without pushdown
Disables filter condition pushdown for specific columns in a query.
  • Engine version 3.1.4 or later: /*+ FILTER_NOT_PUSHDOWN_COLUMNS=[${database}.${tableName}:${col1Name}|${col2Name}] */
  • Engine version earlier than 3.1.4: /*+ NO_INDEX_COLUMNS=[${tableName}.${col1Name};${col2Name},${tableName1}.${col1Name}] */
Query execution mode QUERY_TYPE Specifies the query execution mode of a cluster. Valid values:
  • interactive
  • batch
Note Different query execution modes are supported for clusters in different editions.
SET adb_config QUERY_TYPE=interactive; Query execution modes
Query queue XIHE_ENV_QUERY_MAX_CONCURRENT_QUERIES Specifies the maximum number of general queries that can be executed on a single frontend node. Valid values: 1 to 20. Default value: 20. SET adb_config XIHE_ENV_QUERY_MAX_CONCURRENT_QUERIES=20; Query throttling configurations
XIHE_ENV_QUERY_MAX_QUEUED_QUERIES Specifies the maximum number of general queries that can be queued on a single frontend node. Valid values: 1 to 200. Default value: 200. SET adb_config XIHE_ENV_QUERY_MAX_QUEUED_QUERIES=20;
XIHE_ENV_QUERY_ETL_MAX_CONCURRENT_SIZE Specifies the maximum number of extract-transform-load (ETL) queries that can be executed on a single frontend node. Valid values: 1 to 20. SET adb_config XIHE_ENV_QUERY_ETL_MAX_CONCURRENT_SIZE=20;
XIHE_ENV_QUERY_ETL_MAX_QUEUED_SIZE Specifies the maximum number of ETL queries that can be queued on a single frontend node. Valid values: 1 to 100. SET adb_config XIHE_ENV_QUERY_ETL_MAX_QUEUED_SIZE=100;
COORDINATOR_QUERY_QUEUE Specifies the queue used by a query. Valid values:
  • low_priority
  • etl
/*+COORDINATOR_QUERY_QUEUE=low_priority*/ select * from tableName limit 100;
Execution priority DIRECT_LOW_PRIORITY_CPU_QUEUE Specifies the execution priority of a query. /*+DIRECT_LOW_PRIORITY_CPU_QUEUE=true*/ select * from tableName limit 100;