This topic describes the system variables of OceanBase AI Database. The system variables are categorized by their functions.
Global level
Security
Variable name |
Feature description |
|---|---|
| validate_password_check_user_name | Specifies whether the user password can be the same as the username. |
| validate_password_length | The minimum length of a user password. |
| validate_password_mixed_case_count | Specifies the minimum number of uppercase letters and the minimum number of lowercase letters that a user password must contain. |
| validate_password_number_count | Specifies the minimum number of digits required in a user password. |
| validate_password_policy | Used to set the password check policy. |
| validate_password_special_char_count | Specifies the minimum number of special characters that a user password must contain. |
| ob_tcp_invited_nodes | It is used to set the IP allowlist for a tenant. Supports percentages (%), underscores (_), and IPs (separated by commas for multiple IPs). Supports IP list matching, mask matching, and fuzzy matching. |
| default_password_lifetime | The password expiration time. |
| block_encryption_mode | Specifies the encryption algorithm to use in the aes_encrypt and aes_decrypt functions. |
| sql_safe_updates | Specifies whether to enable the SQL security mode of MySQL. The default value is off. |
| super_read_only | It is used to control the read and write permissions of the database. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| pid_file | Retrieves the pathname of the file on which the server writes its process ID. |
| port | This parameter specifies the port number on which the server listens for TCP/IP connections during OBServer deployment. |
| socket | Used to query local client connections.SocketThe name of the file. |
AP-related
Variable name |
Feature description |
|---|---|
| ap_query_cost_threshold | The cost threshold for adaptive selection of columnar storage replicas. |
| ap_query_route_policy | Controls the adaptive selection strategy for AP queries to replicas. |
| ap_query_replica_fallback | When the automatic query routing feature is enabled, this parameter controls whether queries will roll back to non-columnar replicas for execution when no available columnar replica is found. |
Version information
Variable name |
Feature description |
|---|---|
| version_comment | This API is used to view the version information of an OBServer node. |
| version | Used to view the server version number. |
| ob_last_schema_version | Sets the version number of the schema most recently used in the current session. |
| ob_proxy_global_variables_version | This API is used to set the latest version information of global variables that an OBServer node returns to OBProxy. |
| ob_enable_transmission_checksum | This parameter specifies whether to perform packet checksum verification between the OBProxy and OBServer nodes. The setting takes effect immediately. |
| ob_compatibility_control | It is used to control the behavior mode in case of compatibility conflicts with MySQL 5.7 and MySQL 8.0. |
| ob_compatibility_version | The version of OceanBase AI Database that is compatible with the feature for controlling changes in product behavior. |
| ob_security_version | Specifies the version of OceanBase AI Database that is compatible with security features. The compatibility version must be specified when creating a tenant and cannot be modified after the tenant is created. |
| old_alter_table | It specifies whether to enable the legacy ALTER TABLE syntax and operations. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
Debugging
Variable name |
Feature description |
|---|---|
| debug | Used to set debugging options. The default value isd:t:i:o,/tmp/mysqld.trace.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ob_global_debug_sync | Used to set the synchronization point during debugging. Setting this variable affects all sessions. |
Case sensitivity
Variable name |
Feature description |
|---|---|
| lower_case_table_names | Specifies whether the search is case-sensitive. |
Read/write and query
Variable name |
Feature description |
|---|---|
| query_cache_size | This parameter specifies the memory allocated for storing historical query results, that is, the unused memory. |
| query_cache_type | Used to query the cache type. |
| ob_query_timeout | Sets the query timeout period. |
| is_result_accurate | When a query containstopkWhen prompted,is_result_accurateIndicates whether the result is correct. |
| net_buffer_length | Sets the maximum size of an SQL query that an OBServer node can accept. |
| read_only | Specifies whether the tenant is in read-only mode. |
| ob_read_consistency | Sets the read consistency level. |
| ob_max_read_stale_time | Maximum latency threshold for weak read queries (in μs). |
| net_read_timeout | The number of seconds to wait for other data on the connection before interrupting the read. |
| net_write_timeout | Sets the number of seconds to wait for block writes to complete before interrupting the write. |
| ob_enable_index_direct_select | Specifies whether users are allowed to directly query index tables. |
| ob_enable_aggregation_pushdown | Specifies whether to allow pushdown of aggregate operations. |
| ob_enable_jit | Sets the JIT execution engine mode. |
| sql_throttle_network | Specifies the request queue time. If the request queue time is greater than or equal to this value, the query is not allowed to be executed. |
| parallel_servers_target | Sets the queuing conditions for large queries on each server. |
| cte_max_recursion_depth | Sets the maximum recursion depth for common table expressions (CTEs). The server terminates operations that exceed this CTE value. |
| regexp_stack_limit | The maximum available memory for the internal stack used by regular expression matching operations. |
| regexp_time_limit | The time limit for regular expression matching operations. |
| long_query_time | The threshold for identifying slow queries. |
Scheduler-related
Variable name |
Feature description |
|---|---|
| event_scheduler | Determines whether the event scheduler is enabled and running on the server. |
Replica-related
Variable name |
Feature description |
|---|---|
| master_info_repository | Specifies whether metadata is stored as records in the mysql table of the system database InnoDB or as files in the data directory. The default value isFILE.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| replication_optimize_for_static_plugin_config | Controls whether to enable shared locks to improve the performance of semi-synchronous replication. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| replication_sender_observe_commit_only | Controls whether to enable rate-limiting callbacks to improve the performance of semi-synchronous replication. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without an error being returned. |
| rpl_semi_sync_slave_enabled | Controls whether to enable semi-synchronous replication on the replica. Default value:OFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| rpl_semi_sync_slave_trace_level | Specifies the debug tracking level for semi-synchronous replication on the primary replica. Default value:32, indicating the network wait level.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| rpl_stop_slave_timeout | Specifies the amount of time to wait before stopping the slave when the STOP SLAVE command times out. The unit is seconds. Default value:31536000.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| slave_checkpoint_group | Sets the maximum number of transactions that multi-threaded replication can handle before calling the checkpoint operation to update the progress status. The default value is512.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| slave_checkpoint_period | Specifies the maximum amount of time allowed before calling checkpoint operations to update the status of multi-threaded replication, in milliseconds. The default value is300.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without an error being returned. |
| slave_compressed_protocol | When both the source and replica support compression, controls whether to use compression according to the source or replica protocol. Default value:OFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| slave_exec_mode | Specifies how to resolve conflicts and errors during replication by configuring the replication thread. Valid values:IDEMPOTENTErrors for duplicate keys and keys not found can be suppressed. Set toSTRICT, duplicate key errors and not found key errors will not be suppressed. The default value isSTRICT.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| slave_max_allowed_packet | Sets the maximum packet size for replication SQL and I/O threads, in bytes. The default value is1073741824
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting takes effect without returning an error. |
| slave_net_timeout | The time, in seconds, that a replica waits for more data or a heartbeat signal from the source before it considers the connection disconnected, stops reading, and attempts to reconnect. The default value is60
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting takes effect without returning an error. |
| slave_parallel_type | Specifies the type of parallel execution to use for replicating transactions when multi-threaded replication is enabled. The default value isDATABASE
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being returned. |
| slave_parallel_workers | Sets the number of threads for parallel execution of replicated transactions. Default value:0, which indicates to disable parallel execution of replication transactions.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| slave_pending_jobs_size_max | For multi-threaded replication, specifies the maximum length of the work queue for storing unapplied events, in bytes. The default value is16777216
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| slave_preserve_commit_order | For multi-threaded replication, controls whether transactions are committed in the order of transactions in the relay log. Default value:OFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting takes effect without an error being returned. |
| slave_rows_search_algorithms | Specifies the algorithm used by the replica to search for related rows. Default value:TABLE_SCAN,INDEX_SCAN.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| slave_sql_verify_checksum | Controls whether the replication SQL thread uses the checksums read from the relay logs to verify data. Default value:OFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting takes effect without an error being returned. |
| slave_transaction_retries | When a replication SQL thread is blocked due to a deadlock or transaction execution exceeding the variableinnodb_lock_wait_timeoutThe number of times the system automatically retries a transaction when it fails due to the specified value. The default value is10.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| slave_type_conversions | Controls the type conversion mode on replicas during row-based replication. The default value is empty, which prohibits type conversion between the source and replicas.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| sql_slave_skip_counter | Sets the number of source events that a replica must skip. Default value:0.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| skip_slave_start | Controls whether to skip starting the replication thread when the replica server starts. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| slave_load_tmpdir | Specifies the directory name for creating temporary files by a replica. The default value is empty.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query it, but you cannot set it. |
| slave_skip_errors | Specify the errors to skip during replication. Default value:OFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried but cannot be set. |
| sync_master_info | The impact of this variable on the replica depends on the replica'smaster_info_repositorySpecifies whether to set the data type to FILE or TABLE. The default value is10000
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| init_slave | This variable is similar to init_connect and is used to specify a string that the slave server executes each time a replication SQL thread starts. Its default value isnull
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| log_slow_slave_statements | Specifies whether to record slow SQL statements executed by replication threads in the slow query logs of the secondary server. If this parameter is not specified, the default value is used.OFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| report_host | The hostname or IP address reported to the source during replica registration. Default value:null.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| report_password | The password of the replication user account reported to the source during replica registration. The default value isnull
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| report_port | The TCP/IP port number used to connect to the replica, reported to the source during replica registration. The default value isnull
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| report_user | Username of the account that reports to the source during replica registration. Default value:null
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query this variable, but you cannot set it. |
| relay_log | The name of the relay log. The default value isnull
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. It can be queried but cannot be set. |
| relay_log_basename | The name and full path of the relay log. The default value is/usr/local/mysql/data/obrd-relay-bin.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| relay_log_index | The name of the relay log index file. The default value is/usr/local/mysql/data/obrd-relay-bin.index
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried but cannot be set. |
| relay_log_info_file | The name of the file that records relay log information. Default value:relay-log.info
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query it, but you cannot set it. |
| relay_log_recovery | If this variable is enabled, automatic relay log recovery is enabled immediately after the slave server starts. Its default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| relay_log_space_limit | The maximum capacity for all relay logs, in bytes. The default value is0.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
Source replication related
Variable name |
Feature description |
|---|---|
| rpl_semi_sync_master_enabled | Controls whether to enable semi-synchronous replication on the source. The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| rpl_semi_sync_master_timeout | Specifies the amount of time, in milliseconds, that the source waits for replica confirmation after a commit. The default value is10000.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| rpl_semi_sync_master_trace_level | Specifies the debug tracking level for semi-synchronous replication on the source. Default value:32, indicating the network wait level.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| rpl_semi_sync_master_wait_for_slave_count | Specifies the number of replica acknowledgments each transaction must receive before the source can proceed. The default value is1.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| rpl_semi_sync_master_wait_no_slave | Controls whether to continue service even when the number of replicas drops below the variablerpl_semi_sync_master_wait_for_slave_countWhen configuring the quantity, whether the source will also wait for a timeout (variablerpl_semi_sync_master_timeout(The set time). Default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| rpl_semi_sync_master_wait_point | Specifies the point in time that a semi-synchronous source waits for a replica to acknowledge transaction receipt before returning a status to the client committing the transaction. The default value isAFTER_SYNC
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
Recycle Bin
Variable name |
Feature description |
|---|---|
| recyclebin | Specifies whether to enable the recycle bin feature. |
| ob_enable_truncate_flashback | Specifies whether to enable flashback for truncated tables. |
Cache-related
Variable name |
Feature description |
|---|---|
| ob_enable_plan_cache | Specifies whether to enable plan cache. |
| ob_plan_cache_percentage | Sets the percentage of memory available for plan caching from the tenant's total memory. |
| ob_plan_cache_evict_high_percentage | Sets the percentage of the maximum memory that the plan cache eviction uses. |
| ob_plan_cache_evict_low_percentage | Sets the percentage of the maximum memory that the cache for stop-mining plans can occupy. |
| ob_bnl_join_cache_size | Specifies how much data is cached in a batch during batch nested loop join. |
| stored_program_cache | Specifies the number of caches for stored procedures and functions. The default value is256.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being returned. |
| table_definition_cache | Sets the amount of memory space used to cache table definitions. The default value is-1.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting takes effect without an error message. |
| table_open_cache_instances | Specifies the number of instances for opening table cache. The default value is16.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
Functions
Variable name |
Feature description |
|---|---|
| interactive_timeout | Specifies the number of seconds the server waits for active interactions before closing interactive connections. |
| wait_timeout | Specifies the number of seconds the server waits for active non-interactive connections before closing them. |
| group_concat_max_len | Used to set the allowedGROUP_CONCAT()The maximum length of the function result. |
InnoDB storage engine related
Variable name |
Feature description |
|---|---|
| innodb_change_buffering_debug | Used to set the debug level for changing the InnoDB buffer pool. The default value is0.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without returning an error. |
| innodb_compress_debug | The debug level used to adjust and control the compression behavior. The default value is0.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| innodb_disable_resize_buffer_pool_debug | Specifies whether to enable the size adjustment of the InnoDB buffer pool. The default value is1.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| innodb_fil_make_page_dirty_debug | The number of dirty pages to be intentionally generated in InnoDB during debugging. Default value:0.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| innodb_limit_optimistic_insert_debug | Specifies the number of records per B-tree page. The default value is0.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without an error being returned. |
| innodb_merge_threshold_set_all_debug | Specifies the page full percentage for the index page. The default value is50.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting takes effect without an error being returned. |
| innodb_saved_page_number_debug | Sets the number of page numbers saved during InnoDB debugging. The default value is0.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| innodb_trx_purge_view_update_only_debug | This parameter specifies the debug level for controlling whether only the cleanup views are updated during transaction cleanup. The default value is0.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without an error being returned. |
| innodb_trx_rseg_n_slots_debug | Specifies the number of slots in a transaction rollback segment. Each slot stores rollback information for transactions. The default value is0.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| innodb_stats_persistent | Controls whether to persist InnoDB index statistics to disk. |
| innodb_force_recovery | Crash recovery mode, used to repair data in the damaged InnoDB storage engine. The default value is0
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query it, but you cannot set it. |
| innodb_replication_delay | When the variable reachesinnodb_thread_concurrencyWhen configuring the value, it indicates the delay time of the replication thread on the replica server, in milliseconds. The default value is0.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| innodb_large_prefix | It specifies whether to allow index key prefixes longer than 767 bytes (up to 3,072 bytes) for InnoDB tables using the DYNAMIC or COMPRESSED row format. The default value isON.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| innodb_sort_buffer_size | Specifies the buffer size for sorting operations. The default value is1048576.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| default_tmp_storage_engine | Specifies the default storage engine for temporary tables. The default value isInnoDB.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| innodb_tmpdir | Specifies the directory used by InnoDB to store temporary files.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error. |
| mecab_rc_file | Specifies the configuration file path of MeCab.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query it, but you cannot set it. |
| innodb_temp_data_file_path | Specifies the storage path for InnoDB temporary data files. The default value isibtmp1:12M:autoextend, indicating that InnoDB will use a temporary data file named ibtmp1 with an initial size of 12 MB. This file will automatically expand as needed to store additional temporary data.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query it, but you cannot set it. |
| innodb_data_file_path | Specifies the storage path and file name of the InnoDB data file. The default value isibdata1:12M:autoextend, indicating that InnoDB will use a temporary data file named ibdata1 with an initial size of 12 MB. This file will automatically expand as needed to store additional temporary data.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query it, but you cannot set it. |
| innodb_data_home_dir | Sets the root directory for InnoDB data files.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; queries are allowed, but settings cannot be made. |
| innodb_read_only | Specifies whether to start InnoDB in read-only mode. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query this variable, but you cannot set it. |
| innodb_rollback_on_timeout | Specifies whether to abort and roll back the entire transaction when a transaction timeout occurs. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| innodb_api_disable_rowlock | Specifies whether to disable row locks when InnoDB Memcached performs DML operations. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| innodb_autoinc_lock_mode | The locking mode used to generate auto-increment values. Default value:1.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| low_priority_updates | It is used to specify whether to control the priorities of INSERT, UPDATE, DELETE, and REPLACE statements. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| max_error_count | Specifies the maximum number of errors, warnings, and notifications that the server can store in the diagnostic context. The default value is64.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| max_insert_delayed_threads | Specifies the maximum number of threads for executing INSERT DELAYED statements. The default value is20.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| innodb_monitor_disable | This variable acts as a switch to control which metric counters are disabled.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| innodb_monitor_enable | This variable acts as a switch to control which metric counters are enabled.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| innodb_monitor_reset | This variable acts as a switch to control which metric counters have their counts reset to 0.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| innodb_monitor_reset_all | This variable acts as a switch to control whether to reset all values (such as the maximum and minimum values) of which metric counters to 0.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| innodb_old_blocks_pct | Specifies the approximate percentage of the old data block sub-list in the InnoDB buffer pool. The default value is37
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| innodb_old_blocks_time | Specifies the duration in milliseconds that a block must be retained in the old sub-list after its first access before it can be moved to the new sub-list. The default value is1000.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| innodb_purge_batch_size | Specifies the number of undo log pages to be parsed and processed from the history list at once. The default value is300.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without an error being returned. |
| innodb_purge_rseg_truncate_frequency | Controls the frequency at which rollback segments are cleared, that is, how many times the system calls are required before a rollback segment is released. The default value is128.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| innodb_random_read_ahead | Enables random pre-read technology to optimize InnoDB I/O. Default value:OFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| innodb_read_ahead_threshold | Controls the linear prefetch behavior of the InnoDB storage engine. The default value is56, indicating that InnoDB must sequentially read at least 56 pages from a segment to initiate asynchronous reading of the next segment.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| innodb_rollback_segments | Specifies the number of rollback segments for the transaction used to generate undo records. The default value is128.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| innodb_spin_wait_delay | The time interval between each spinlock wait. The default value is6.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting takes effect without returning an error. |
| innodb_status_output | Enables or disables scheduled output for the standard InnoDB monitor. The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| innodb_status_output_locks | Enables or disables InnoDB lock monitoring. The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| innodb_sync_spin_loops | The number of times a thread waits before it is suspended if an InnoDB mutual exclusion lock has not been released. The default value is30.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error message. |
| internal_tmp_disk_storage_engine | Specifies the storage engine for internal temporary tables on disk. The default value isINNODB
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| innodb_fast_shutdown | The shutdown mode of the InnoDB engine. The default value is1
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| innodb_io_capacity | The approximate number of IOPS that InnoDB can perform per second for background tasks. The default value is200.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting takes effect without returning an error. |
| innodb_io_capacity_max | The maximum number of IOPS that a background task can perform per second in an emergency. The default value is2000.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error message. |
| innodb_thread_concurrency | The maximum number of threads allowed internally in InnoDB. The default value is0, indicating no limit.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| innodb_thread_sleep_delay | The time, in microseconds, that an InnoDB thread sleeps before being added to the InnoDB wait queue. The default value is10000
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| innodb_adaptive_hash_index_parts | Specifies the number of partitions for adaptive hash index searches. The default value is8
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| innodb_numa_interleave | Specifies whether to enable the NUMA interleaved memory strategy for buffer pool memory allocation. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. It can be queried but cannot be set. |
| innodb_open_files | Specifies the maximum number of files that can be opened at a time. The default value is2000
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| innodb_page_cleaners | The number of threads that refresh dirty pages in the buffer pool. The default value is1
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| innodb_purge_threads | The number of background threads used for cleanup operations. Default value:4
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. It can be queried but cannot be set. |
| innodb_read_io_threads | The number of I/O threads during read operations. The default value is4
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| innodb_sync_array_size | Specifies the size of the mutex lock wait array. The default value is1
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| innodb_use_native_aio | Whether to use the Linux asynchronous I/O subsystem. Default value:1
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| innodb_write_io_threads | The number of I/O threads for write operations. The default value is4.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query this variable, but you cannot set it. |
| innodb_api_enable_binlog | Specifies whether to allow the InnoDB Memcached plugin to be used together with MySQL binlogs. The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| innodb_locks_unsafe_for_binlog | This variable affects how InnoDB uses gap locking for searches and index scans. Its default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. It can be queried, but cannot be set. |
| innodb_log_buffer_size | Specifies the size of the InnoDB transaction log cache, in bytes. The default value is16777216.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| innodb_log_files_in_group | The number of log files in the log group. Default value:2.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| innodb_log_file_size | The size of each log file in the log group, in bytes. Default value:50331648
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| innodb_log_group_home_dir | Specifies the directory path for InnoDB redo logs. The default value is./.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query this variable, but you cannot set it. |
| innodb_undo_directory | Specifies the directory for the undo tablespaces created by InnoDB. The default value is./.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| innodb_undo_tablespaces | Specifies the number of undo tablespaces available for InnoDB. The default value is0.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
Cluster-related
Variable name |
Feature description |
|---|---|
| ob_capability_flag | It is a capability provided by an OBServer node for capability negotiation when connecting to a proxy, informing the proxy which features the current OBServer node supports and which it does not. |
| ob_compatibility_mode | Specifies the compatibility mode for a tenant. |
| ob_route_policy | It is used to set the routing strategy for selecting data replicas within an OBServer node. |
| performance_schema | Used to indicate to the client whether performance information queries are supported. The default value isOFF.
NoteThis variable is for compatibility with MySQL 8.0 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| resource_manager_plan | Used to activate a resource management plan. Different plans use different CPU quotas to limit user activity within a resource group. |
| license | Used to view the type of the license. |
| ob_proxy_partition_hit | It specifies whether OBProxy sends the data requested by the SQL statement to the OBServer node where the data resides in the primary partition. |
| ob_org_cluster_id | Used to set the for the OceanBase AI Database cluster.CLUSTER_ID. |
| server_uuid | View the UUID of an OBServer node. |
| default_storage_engine | This API is used to view the default storage engine of an OBServer node. |
| slave_allow_batching | Controls whether to enable batch updates for replication threads. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
Directory path related
Variable name |
Feature description |
|---|---|
| datadir | The local disk path for data storage. |
| plugin_dir | Used to view the path where the plugin DLL is stored. |
| secure_file_priv | Controls the accessible paths when importing or exporting to files. |
MyISAM storage engine related
Variable name |
Feature description |
|---|---|
| delay_key_write | Specifies whether to delay writing index keys for MyISAM tables. The default value isON.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting takes effect without an error being returned. |
| key_buffer_size | Sets the key buffer size for the MyISAM storage engine. The default value is8388608.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| key_cache_age_threshold | The threshold for controlling the downgrade of buffers from the hot sub-list to the warm sub-list in the key cache. A lower value indicates a faster downgrade. The default value is300.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| key_cache_block_size | Sets the size of a single block in the MyISAM key cache. The default value is1024.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without returning an error. |
| key_cache_division_limit | Sets the maximum number of partitions for the MyISAM key cache. The default value is100.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| max_seeks_for_key | Sets the maximum number of address operations allowed in a MyISAM query. The default value is18446744073709551615.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| skip_external_locking | Specifies whether to disable the external locking mechanism for MyISAM tables. The default value isON.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
Temporary files
Variable name |
Feature description |
|---|---|
| max_tmp_tables | Limits the maximum number of temporary tables a user session can hold simultaneously. The default value is32
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error. |
Memory
Variable name |
Feature description |
|---|---|
| ob_sql_work_area_percentage | The percentage of tenant memory used for SQL execution. |
| ob_sql_audit_percentage | Sets the percentage of the current tenant's memory that the SQL audit memory limit occupies. |
| ob_reserved_meta_memory_percentage | It specifies the percentage of reserved memory for the tenant, which is primarily used to store metadata-related structural information. |
| ob_temp_tablespace_size_percentage | Percentage limit for the size of temporary tablespaces on a tenant's disk. |
NDB storage engine related
Variable name |
Feature description |
|---|---|
| ndb_allow_copying_alter_table | Whether to AllowALTER TABLEstatements and other DDL statements for table replication operations. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| ndb_autoincrement_prefetch_sz | Specifies the number of prefetches for auto-increment columns. This value affects the performance and concurrent access capability of auto-increment columns. Default value:1.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ndb_blob_read_batch_bytes | Configures the maximum size for batch reading of BLOB data in an NDB cluster, in bytes. The default value is65536.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| ndb_blob_write_batch_bytes | Configures the size of BLOB data that can be written in a batch in an NDB cluster. The unit is bytes. The default value is65536.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without an error being returned. |
| ndb_cache_check_time | Specifies the time interval in milliseconds for checking whether the cache needs to be refreshed on each NDB node. The default value is0.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ndb_clear_apply_status | Specifies whether to clear the application state. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without an error message. |
| ndb_data_node_neighbour | Defines the neighbor relationship of a data node. Default value:0.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting takes effect without an error message. |
| ndb_default_column_format | Defines the default column format for a table, specifying whether to store data in fixed-length or variable-length format. The default value isFIXED, indicating that the data is stored in a fixed-length format.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error message. |
| ndb_deferred_constraints | Controls whether to delay constraint checking on a table. The default value is0.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without an error message. |
| ndb_distribution | Specifies the default distribution method for an NDB table: whether to partition by hash key value or by linear hash. The default value isKEYHASH, indicating to use hash key value partitioning.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error message. |
| ndb_eventbuffer_free_percent | Specifies the percentage of free space in the NDB cluster event cache. The default value is20.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| ndb_eventbuffer_max_alloc | Specifies the maximum memory size that can be allocated for event caching, in bytes. The default value is0, which indicates no limit.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| ndb_extra_logging | Used to record information of the specified NDB storage engine in the MySQL error log. The default value is1.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ndb_force_send | Whether to forcibly send the cache to NDB immediately without waiting for other threads. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error message. |
| ndb_fully_replicated | Determines whether the new table is fully copied. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without returning an error. |
| ndb_index_stat_enable | Specifies whether to use the NDB index statistics collection feature. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| ndb_index_stat_option | Specifies the options for generating NDB index statistics. The default value isloop_checkon=1000ms,loop_idle=1000ms,loop_busy=100ms,update_batch=1,read_batch=4,idle_batch=32,check_batch=32,check_delay=1m,delete_batch=8,clean_delay=0,error_batch=4,error_delay=1m,evict_batch=8,evict_delay=1m,cache_limit=32M,cache_lowpct=90
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ndb_join_pushdown | Controls whether to enable the connection pushdown optimization feature in the storage engine. The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| ndb_log_binlog_index | Controls whether to insert the epoch-to-binlog-position mapping into the ndb_binlog_index table. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ndb_log_empty_epochs | Controls whether unchanged epoch transactions are written to the binlog. The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| ndb_log_empty_update | Controls whether unchanged UPDATE transactions are written to the binlog. The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ndb_log_exclusive_reads | Determines whether to use an exclusive lock to record primary key reads. Default value:OFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ndb_log_update_as_write | Controls whether updates on the source are written to the binlog as updates (OFF) or writes (ON). The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being returned. |
| ndb_log_update_minimal | Controls the logging behavior of the NDB cluster. Valid values:ONindicates that the NDB cluster records only the minimal information for update operations; the value isOFF, indicating that the NDB cluster records changes for the entire row. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without an error being returned. |
| ndb_log_updated_only | Controls whether MySQL will write only the updated rows or the complete rows when writing updates to the binlog. The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| ndb_optimization_delay | Specifies the wait time, in microseconds, between each group of rows when executing the OPTIMIZE TABLE statement on an NDB table. The default value is10.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| ndb_read_backup | Specifies whether to allow reading data from any segment replica of any NDB table created later. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ndb_recv_thread_activation_threshold | Specifies the activation threshold for the receiving thread. The default value is8
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error message. |
| ndb_recv_thread_cpu_mask | Specifies the CPU mask for the thread that receives requests. The default value is an empty string.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting takes effect without returning an error. |
| ndb_report_thresh_binlog_epoch_slip | Specifies the maximum allowed skip size before reporting a binlog timestamp skip. The default value is10.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ndb_report_thresh_binlog_mem_usage | Specifies the percentage threshold of available binlog memory before a report is sent. That is, when the remaining available binlog memory falls below this value, the system will send a report. The default value is10.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| ndb_row_checksum | Specifies the checksum value of a table row. The value is1When set to yes, the checksum value of each row is calculated and stored. The value is0When this parameter is set to N, table row data verification and detection are not performed. The default value is N.1.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| ndb_show_foreign_key_mock_tables | Whether to display the mock table for foreign key dependencies. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| ndb_slave_conflict_role | Specifies the role of this node in a circular replication (primary-primary) setup. The default value isNONE, indicating that the variable is undefined or not configured.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| ndb_table_no_logging | Controls the logging behavior of NDB tables. The value isONWhen this parameter is set to NDB, all tables created or altered using the NDB storage engine are in a logless state. The default value is NDB.OFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| ndb_table_temporary | Specifies the behavior of temporary tables when the NDB storage engine is used. Valid values:ONWhen this parameter is set to a value less than the maximum allowed, the NDB table will not be written to disk. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| ndb_use_exact_count | Specifies whether to force NDB to use the SELECT count(*) record count to accelerate such queries during query plan generation. The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting takes effect without an error message. |
| ndb_use_transactions | Controls whether to enable NDB transaction support. The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| ndbinfo_max_bytes | For testing and debugging only. The default value is0
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being returned. |
| ndbinfo_max_rows | For testing and debugging only. The default value is10
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without an error being returned. |
| ndbinfo_offline | Whether to set thendbinfoSets the database to offline. Default value:OFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ndbinfo_show_hidden | Whether to display in the MySQL clientndbinfoThe underlying internal table of the database. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| myisam_data_pointer_size | Specify when unspecifiedMAX_ROWSThe default pointer size for the created MyISAM table when this option is specified, in bytes. The default value is6.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| myisam_max_sort_file_size | Specifies the maximum size of temporary files allowed when recreating a MyISAM index (during REPAIR TABLE, ALTER TABLE, or LOAD DATA), in bytes. The default value is9223372036853720064.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| myisam_repair_threads | Specifies the number of concurrent threads used to repair a MyISAM table. The default value is1
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| myisam_sort_buffer_size | Specifies the cache size allocated for sorting MyISAM indexes during a REPAIR TABLE operation or for creating indexes using CREATE INDEX (or ALTER TABLE), in bytes. The default value is8388608.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| myisam_stats_method | Specifies how the server calculates NULL values when collecting statistics on index value distributions for MyISAM tables. The default value isnulls_unequal, which means that NULL values are treated as regular values and handled in the same way as other values.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| myisam_use_mmap | Whether to use memory mapping for reading from and writing to MyISAM tables. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| server_id_bits | The lowest significant bit in a 32-bit server_id that actually identifies the server. The default value is32
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
Full-text indexes
Variable name |
Feature description |
|---|---|
| innodb_ft_enable_diag_print | This parameter specifies whether to enable or disable the debug output for InnoDB full-text indexes. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| innodb_ft_num_word_optimize | Specifies the minimum number of partitions that must be operated on during an OPTIMIZE TABLE operation. The default value is2000
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| innodb_ft_result_cache_limit | Specifies the size of the result cache for InnoDB full-text indexes. The default value is2000000000, in bytes.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error. |
| innodb_ft_server_stopword_table | It specifies the server stopword list for InnoDB full-text indexes. The default value isNULL
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| innodb_optimize_fulltext_only | Controls the behavior of the OPTIMIZE TABLE statement on InnoDB tables containing FULLTEXT indexes. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| innodb_ft_cache_size | Sets the cache size for InnoDB full-text indexes. The default value is8000000, in bytes.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| innodb_ft_sort_pll_degree | The number of parallel threads used for full-text index sorting. The default value is2.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| innodb_ft_total_cache_size | Sets the total cache size for InnoDB full-text indexes. The default value is640000000, in bytes.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| ft_stopword_file | The path of the file used to specify stopwords. Default value:built-in.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. It can be queried but cannot be set. |
Runtime Filter
Variable name |
Feature description |
|---|---|
| runtime_filter_type | Sets the runtime filter type at the tenant level. |
| runtime_filter_wait_time_ms | Sets the maximum wait time for the runtime filter. |
| runtime_filter_max_in_num | It is used to set the number of NDVs (the number of distinct values in a column) for Runtime In Filter. |
| runtime_bloom_filter_max_size | Sets the maximum memory size for the runtime Bloom filter, in bytes. |
Upgrade related
Variable name |
Feature description |
|---|---|
| avoid_temporal_upgrade | Used to manage the upgrade behavior for time-sensitive data (such as dates and times). The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error message. |
Time zone and date related
Variable name |
Feature description |
|---|---|
| time_zone | Sets the time zone for the current tenant session. Valid values:'+08:00'The offset format of the andAsia/ShanghaiThe region format value. |
| timestamp | TIMESTAMPis a timestamp in seconds. This variable affectsselect now(6). |
| system_time_zone | Sets the system time zone of the server. |
| error_on_overlap_time | Specifies whether to report an error when ambiguity occurs in the time of daylight-saving time overlapping zones. |
Transactions and transaction logs
Variable name |
Feature description |
|---|---|
| autocommit | Specifies whether to automatically commit transactions. |
| tx_isolation | Sets the transaction isolation level. |
| ob_proxy_set_trx_executed | Used to specify whether the user is sent through OBProxy.START TRANSACTION SyntaxTo the OBServer. |
| ob_trx_idle_timeout | Sets the transaction idle timeout period, which is the duration after which a transaction times out if the execution interval between two statements exceeds this value. |
| transaction_isolation | Sets the isolation level of a transaction. |
| transaction_read_only | Controls whether to allow only read-only transactions. |
| ob_trx_lock_timeout | Sets the lock wait timeout for transactions. |
| tx_read_only | Specifies whether the transaction is read-only. |
| ob_trx_timeout | Sets the transaction timeout period. |
| ob_trace_info | Used to pass-through trace information, which can ultimately be persisted in the redo log. |
| gtid_executed | A collection for storing all committed transactions and the GTIDs set by statements. Its default value is NULL.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried but cannot be set. |
| gtid_owned | A list of all GTIDs currently in use and the IDs of the threads that hold them. The default value is NULL.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
Audit-related
Variable name |
Feature description |
|---|---|
| ob_enable_sql_audit | Controls whether to enable the SQL audit feature for the current tenant. |
Data types
Variable name |
Feature description |
|---|---|
| explicit_defaults_for_timestamp | Specifies whether to enable nonstandard behavior for the TIMESTAMP data type when processing default and null values. |
| log_row_value_options | Controls whether to use partial updates for LOB data. |
| ob_default_lob_inrow_threshold | Specifies the default in-row storage threshold for LOB fields in a table during table creation. |
SQL/PL related
Variable name |
Feature description |
|---|---|
| connect_timeout | Sets the connection timeout period. |
| ob_pl_block_timeout | Sets the maximum timeout period for PL. |
| cursor_sharing | Determines whether to parameterize SQL statements during processing. |
| have_profiling | Used to detect whether query performance analysis is supported. Default value:NO.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query this variable, but you cannot set it. |
| profiling | It is used to enable or disable the statement analysis feature. The default value is0.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| profiling_history_size | Specifies the number of historical query performance records to retain. The default value is15.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| innodb_strict_mode | Sets the SQL check mode for a specific syntax. |
| max_connections | Sets the maximum number of connections for the entire tenant. |
| sql_mode | It is used to set the SQL mode. Different SQL modes have a significant impact on operations such as insertion. |
| sql_quote_show_create | Used to set whether it is aSHOW CREATE TABLEandSHOW CREATE DATABASEThe statement initiates a reference identifier. |
| ob_enable_rich_error_msg | It is used to control whether to display information such as svr_ip, time, and trace_id when an error occurs during SQL execution. |
| sql_throttle_current_priority | Used to set the throttling priority. Onlysql_throttle_current_priorityLess thansql_throttle_priorityOnly the requests on those sessions will be throttled. |
| sql_throttle_priority | Used to set the throttling priority. |
| sql_throttle_rt | Specifies the RT value. |
| max_allowed_packet | Sets the maximum packet size. |
| max_user_connections | Specifies the number of connections a single user can establish to an OBServer node. Set it to0indicates that the number of connections is not limited. |
| max_sp_recursion_depth | Sets the maximum recursion depth for calling any specified stored procedure. |
| sql_select_limit | This clause is used to set the maximum number of rows that a SELECT query is allowed to return. |
| max_connections | Sets the maximum number of connections for the entire tenant. |
| ob_enable_pl_async_commit | Controls whether to enable PL asynchronous commit optimization. |
| sql_transpiler | It is used to control whether to enable the SQL Transpiler feature. |
| plsql_can_transform_sql_to_assign | Used to control the PLselect into from dualWhether to allow rewriting toassignstatement. |
System logs
Variable name |
Feature description |
|---|---|
| binlog_row_image | Specifies whether to record full-column logs. |
| ob_enable_show_trace | Specifies whether to use trace logs. |
| ob_log_level | Sets the log level for the current session. If not specified, the system log level is used. |
| tracefile_identifier | Used to add specified content to logs, facilitating filtering and iterative tracking of log lines. |
| master_verify_checksum | Controls whether to enable checksum verification. Default value:OFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting takes effect without an error being reported. |
| log_statements_unsafe_for_binlog | Whether to record error code 1592 information in the error log. The default value is1.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| binlog_gtid_simple_recovery | Controls how the server iterates through binlog files during GTID search upon startup or restart. The default value is1, indicatinggtid_executedandgtid_purgedThe value of this parameter will be determined at startup based on the timestamps in the oldest and newest binlog files.previous_gtids_log_eventis calculated based on its value.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| log_bin_basename | The full path of the binlog file. The default value isnull
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| log_bin_index | The name and path of the binlog index file. The default value isnull
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query it, but you cannot set it. |
| log_slave_updates | Specifies whether the replica server records updates received from its primary server's binlog into its own binlog. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried but cannot be set. |
System servers
Variable name |
Feature description |
|---|---|
| preload_buffer_size | Specifies the cache size in bytes for preloading indexes. The default value is32768.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error message. |
| read_buffer_size | Specifies the cache size in bytes that can be used during data reading. The default value is131072.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| read_rnd_buffer_size | Specifies the cache size for reading data from a MyISAM table. It is also used for multi-range read optimization for any storage engine, in bytes. The default value is262144.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| sync_frm | Whether to synchronize the metadata of InnoDB tables to disks..frmfiles. The default value is1
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting takes effect without an error message. |
| keep_files_on_create | When not in useDATA DIRECTORYorINDEX DIRECTORYWhen you use the option to specify the storage location for data files or index files, this variable controls whether the server retains existing files in the corresponding directory when creating a MyISAM table. Its default value isOFF, which means to overwrite the existing file.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| max_heap_table_size | Specifies the maximum size to which a memory table created by the user is allowed to grow, in bytes. The default value is16777216.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| bulk_insert_buffer_size | Specifies the cache size for batch data insertion, in bytes per thread. The default value is8388608.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without returning an error. |
| general_log_file | Specifies the name of the log file for regular queries. The default value format ishost_name.log.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| host_cache_size | Specifies the size of the host cache. The default value is279.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| log_error_verbosity | Defines the verbosity with which the server writes error, warning, and comment information to the error log. The default value is3
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| log_output | Specifies the output targets for regular query logs and slow query logs. The default value isFILE
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| log_queries_not_using_indexes | Whether to log queries that do not use indexes to the slow query log. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| log_slow_admin_statements | Specifies whether to record slow management statements such as ALTER TABLE, ANALYZE TABLE, CHECK TABLE, CREATE INDEX, DROP INDEX, OPTIMIZE TABLE, and REPAIR TABLE in the slow query log. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| log_syslog | Whether to log error logs to system logs. Default value:OFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| log_syslog_facility | The tool that writes error logs to the system log. The default value isdaemon
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting takes effect without an error being reported. |
| log_syslog_include_pid | Whether to write the service process ID in the error log output to the system log. The default value is1
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| log_syslog_tag | Specifies the tag to add to the server identifier in the error log output written to the system log. The default value isnull
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| log_throttle_queries_not_using_indexes | The maximum number of statements that can be written to the slow query log per minute. The default value is0, which indicates no limit.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error message. |
| log_timestamps | Controls the time zone for the timestamps of error logs, general logs, and slow query logs written to files. The default value isUTC
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| log_warnings | Specifies the logging level for recording additional alert information in the error log. The default value is2.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting takes effect without returning an error. |
| max_delayed_threads | Maximum number of threads allowed for creating INSERT DELAYED statements. Default value:20
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| offline_mode | Whether to set the server to offline mode. Default value:0, which means not to set it to offline mode.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| require_secure_transport | Whether a secure transmission method is required for the connection between the client and server. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| slow_launch_time | When the time spent creating a thread exceeds this value, the value of the status variable Slow_launch_threads increases by one second. The default value is2.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| sql_log_off | Enables or disables general query logging for the current session. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| thread_cache_size | The maximum number of threads that can be accommodated in the thread cache. The default value is9.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without returning an error. |
| thread_pool_high_priority_connection | Controls whether the thread pool reserves idle threads for high-priority connections. The default value is0
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| thread_pool_max_unused_threads | The maximum number of unused threads allowed in the thread pool. The default value is0
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| thread_pool_prio_kickup_timer | The time required for a statement to move to the high-priority queue, in milliseconds. The default value is1000
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| thread_pool_stall_limit | The maximum time within which a statement must complete after it starts execution, in 10 milliseconds. The default value is6.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| have_statement_timeout | Specifies whether to enable statement execution timeout. The default value isON.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| old | A compatibility variable used to resolve compatibility issues. Its default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query it, but you cannot set it. |
| version_tokens_session_number | The default value of the internally used variable is0.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error message. |
| back_log | The maximum number of connection requests that can be queued while the server is processing them. The default value is80.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query this variable, but you cannot set it. |
| basedir | The path name of the installation root directory. The default value is/usr/local/mysql/.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| bind_address | The IP address to which the server binds when listening for TCP/IP client connections. The default value is*
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| core_file | Whether to generate a core file when a fatal error occurs before the server exits. Default value:OFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| have_compress | Indicates whether the zlib compression library required for the COMPRESS() and UNCOMPRESS() functions is available. The default value isON, indicating it is available.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| ignore_db_dirs | A comma-separated list of names that are not considered database directories in the data directory. The default value isnull
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| init_file | Specifies a file name that contains SQL statements executed by the server upon startup. The default value isnull
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query this variable, but you cannot set it. |
| large_files_support | Indicates whether the server supports processing large files. The default value is1, indicating support.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| large_pages | Specifies whether to enable large-page support. The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query this variable, but you cannot set it. |
| large_page_size | If the large-page support feature is enabled, this variable specifies the size of memory pages, in bytes. The default value is0
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. It can be queried but cannot be set. |
| locked_in_memory | Whether the server is locked in memory. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| log_error | Output target of error log files. Default value:./obrd.16c.vd3-s2h6-n3.err.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query it, but you cannot set it. |
| named_pipe | Whether the server allows clients to connect using named pipes. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query it, but you cannot set it. |
| named_pipe_full_access_group | Specifies which Windows user group has permission to use named pipe connections when named pipe connections are supported. The default value isempty string
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| open_files_limit | The number of file descriptors available to the server. The default value is655360.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| shared_memory | Whether the server allows clients to use shared memory connections. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| shared_memory_base_name | Specifies the name of the shared memory used for the shared-memory connection. The default value isMYSQL
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| skip_name_resolve | Controls whether to resolve the hostname when checking client connections. The default value isOFF, indicating that the hostname needs to be resolved.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| skip_networking | Controls whether the server allows TCP/IP connections. Default value:OFF, which indicates that TCP/IP connections are disabled.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query it, but you cannot set it. |
| thread_handling | The thread model used by the server to handle client connections. The default value isone-thread-per-connection.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| thread_pool_algorithm | Controls the algorithm used by the thread pool plugin. The default value is0, indicating that the conservative low-concurrency algorithm is used.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. It can be queried but cannot be set. |
| thread_pool_size | Specifies the number of thread groups in the thread pool. The default value is16.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| thread_stack | The stack size for each thread. The default value is262144.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| tls_version | The protocols allowed for encrypted connections on the server.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried but cannot be set. |
X Plugin related
Variable name |
Feature description |
|---|---|
| mysqlx_bind_address | Specifies the network address for TCP/IP connections monitored by the X plugin. The default value is*, which indicates accepting TCP/IP connections from all server hosts.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried but cannot be set. |
| mysqlx_port | Specifies the network port on which the X plugin listens for TCP/IP connections. The default value is33060.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. It can be queried but cannot be set. |
| mysqlx_port_open_timeout | Specifies the time, in seconds, that the X plugin waits for a TCP/IP port to become available. The default value is0.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| mysqlx_socket | Specifies the path of the Unix socket file used by the X plugin for connection. The default value is/tmp/mysqlx.sock
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| mysqlx_ssl_ca | Specifies the path of the SSL certificate authority (CA) file used by the X plugin.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; queries can be performed, but settings cannot be modified. |
| mysqlx_ssl_capath | Specifies the directory path of the SSL certificate authority (CA) certificate file used by the X plugin.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| mysqlx_ssl_cert | Specifies the path of the SSL certificate file used by the X plugin.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; queries can be performed, but settings cannot be modified. |
| mysqlx_ssl_cipher | Specifies the list of encryption algorithms used by the SSL encryption of the X plugin.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| mysqlx_ssl_crl | Specifies the filename of the certificate revocation list file used by the X plugin.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; queries are possible, but settings cannot be made. |
| mysqlx_ssl_crlpath | Specifies the directory path for the certificate revocation list files used by the X plugin.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; queries are possible, but settings cannot be made. |
| mysqlx_ssl_key | Specifies the path of the SSL certificate key file used by the X plugin.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; queries can be performed, but settings cannot be modified. |
Performance mode related
Variable name |
Feature description |
|---|---|
| performance_schema_accounts_size | Specified TableaccountsThe number of rows in the table. The default value is-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_digests_size | Specify Tableevents_statements_summary_by_digestThe maximum number of rows in the middle. The default value is10000.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_events_stages_history_long_size | Specify Tableevents_stages_history_longThe number of rows in the table. Default value:10000
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_events_stages_history_size | Specify Tableevents_stages_historyThe number of rows per thread. The default value is10
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query this variable, but you cannot set it. |
| performance_schema_events_statements_history_long_size | Specify Tableevents_statements_history_longThe number of rows in the table. The default value is10000
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_events_statements_history_size | Specify Tableevents_statements_historyThe number of rows per thread. The default value is10
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_events_transactions_history_long_size | Specified Tableevents_transactions_history_longThe number of rows in the table. Default value:10000.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query this variable, but you cannot set it. |
| performance_schema_events_transactions_history_size | Specify Tableevents_transactions_historyThe number of rows per thread. Default value:10
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_events_waits_history_long_size | Specify Tableevents_waits_history_longThe number of rows in the table. The default value is10000
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| performance_schema_events_waits_history_size | Specify Tableevents_waits_historyThe number of rows per thread. The default value is10.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_hosts_size | Specify TablehostsThe number of rows in the table. Default value:-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_cond_classes | Specifies the maximum number of condition collectors. The default value is80.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| performance_schema_max_cond_instances | Specifies the maximum number of condition objects that can be collected. The default value is-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_digest_length | Specifies the maximum length in bytes of an SQL statement in standard format when stored in performance mode. The default value is1024
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_file_classes | Specifies the maximum number of file collectors. The default value is80
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| performance_schema_max_file_handles | Specifies the maximum number of file objects that can be opened. The default value is32768
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_file_instances | Specifies the maximum number of file objects that can be collected. The default value is-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_index_stat | Maximum number of indexes maintained by the performance mode statistics. Default value:-1, indicating automatic resizing.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; queries can be executed, but the variable cannot be set. |
| performance_schema_max_memory_classes | Specifies the maximum number of memory collectors. The default value is320.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query it, but you cannot set it. |
| performance_schema_max_metadata_locks | Specifies the maximum number of metadata lock collectors. The default value is-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_mutex_classes | Specifies the maximum number of mutex collectors. The default value is200
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query it, but you cannot set it. |
| performance_schema_max_mutex_instances | Specifies the maximum number of mutually exclusive objects that can be collected. The default value is-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_prepared_statements_instances | Specify Tableprepared_statements_instancesThe maximum number of rows in the middle. The default value is-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_program_instances | Maximum number of stored programs maintained by the performance mode statistics. Default value:-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_rwlock_classes | Specifies the maximum number of rwlock collectors. The default value is50
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. It can be queried but cannot be set. |
| performance_schema_max_rwlock_instances | Specifies the maximum number of RWLock objects that can be acquired. The default value is-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_socket_classes | Specifies the maximum number of socket collectors. The default value is10
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_socket_instances | Specifies the maximum number of socket objects that can be collected. The default value is-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_sql_text_length | Specifies the maximum length (in bytes) of an SQL statement that can be stored in the SQL_TEXT column of event tables such as events_statements_current, events_statements_history, and events_statements_history_long. The default value is1024
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_stage_classes | Specifies the maximum number of collectors allowed in a stage. The default value is150
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query it, but you cannot set it. |
| performance_schema_max_statement_classes | Specifies the maximum number of statement collectors. The default value is193
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| performance_schema_max_statement_stack | Maximum depth of nested stored program calls maintained in performance mode statistics. Default value:10
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_table_handles | Specifies the maximum number of table objects that can be opened. The default value is-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_table_instances | Specifies the maximum number of table objects that can be collected. The default value is-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_table_lock_stat | Maximum number of tables for which lock statistics are maintained in performance mode. Default value:-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_max_thread_classes | Specifies the maximum number of thread collectors. The default value is50.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. It can be queried but cannot be set. |
| performance_schema_max_thread_instances | Specifies the maximum number of thread objects that can be collected. The default value is-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_session_connect_attrs_size | The pre-allocated memory size for storing connection attribute key-value pairs retained by each thread, in bytes. The default value is512
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_setup_actors_size | Specify Tablesetup_actorsThe number of rows in the table. The default value is-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_setup_objects_size | Specified tablesetup_objectsThe number of rows in the table. Default value:-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| performance_schema_users_size | Specify TableusersThe number of rows in the table. The default value is-1, indicating auto scaling.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
Lock-related
Variable name |
Feature description |
|---|---|
| metadata_locks_cache_size | Sets the cache size for metadata locks. The default value is1024, in bytes.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| metadata_locks_hash_instances | Specifies the number of instances for the metadata lock hash table. The default value is8.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query this variable, but you cannot set it. |
Foreign key related
Variable name |
Feature description |
|---|---|
| foreign_key_checks | Specifies whether to check foreign constraints during DML and DDL operations. |
Materialized view related
Variable name |
Feature description |
|---|---|
| mview_refresh_dop | Controls the default refresh parallelism for materialized views. |
Optimizer-related
Variable name |
Feature description |
|---|---|
| optimizer_use_sql_plan_baselines | Controls whether the optimizer uses plan baselines. |
| optimizer_capture_sql_plan_baselines | Controls whether to automatically capture new plans to the plan baseline. |
| parallel_degree_policy | Used to set the parallelism selection strategy. |
| parallel_degree_limit | This parameter specifies the upper limit of the degree of parallelism (DOP) that the optimizer can select when the auto-DOP strategy is used. |
| parallel_min_scan_time_threshold | Sets the minimum estimated execution time for parallel processing of base table scans. |
| optimizer_dynamic_sampling | Controls the level of dynamic sampling. |
| optimizer_features_enable | This parameter is used to enable optimizer features for different OceanBase AI Database versions. |
| ob_enable_transformation | Specifies whether to enable the rewrite feature of the SQL optimizer. |
| ob_table_access_policy | Controls the optimizer to prefer specific storage formats when generating base table plans. |
| range_index_dive_limit | Specifies the maximum number of ranges allowed for row estimation at the storage layer by the optimizer. |
| cardinality_estimation_model | Controls the correlation assumptions used by the optimizer during cardinality estimation. |
Auto-increment columns
Variable name |
Feature description |
|---|---|
| auto_increment_increment | Sets the auto-increment step size, which is applicable only when logging in through the MySQL client. |
| auto_increment_offset | Used to determineAUTO_INCREMENTThe starting point of the column value. |
| last_insert_id | Retrieves the value of the auto-increment field from the last insert of the current session. |
| identity | identityand variableslast_insert_idare synonyms and can be used interchangeably.select @@identityQuery. |
| sql_auto_is_null | Determines whether to obtain the auto-increment column value of the last inserted row. |
| auto_increment_cache_size | Specifies the number of auto-increment values stored in the cache. |
| div_precision_increment | This parameter specifies the increment for the precision of the division result based on the precision of the dividend. It is a MySQL-compatible feature. |
Character sets and strings
Variable name |
Feature description |
|---|---|
| character_set_client | Sets the character set for statements sent by the client. |
| character_set_connection | Sets the character set to be converted after receiving a statement. |
| character_set_database | Sets the character set of the default database. |
| character_set_results | Sets the character set to which the server should convert the result set or error message before sending it back to the client. |
| character_set_server | Sets the server character set. |
| character_set_system | This view is used to view the character set used by the server. |
| collation_connection | Sets the character set and collation for the connection. |
| collation_database | Sets the default character set and collation for creating a database. |
| collation_server | Sets the default character set and collation for the server. |
| character_set_filesystem | Sets the character set type of the file system. |
| sql_warnings | This parameter specifies whether to generate an information string for a single-row INSERT statement when an alert is triggered. |
| init_connect | Sets the string executed by the server for each client connection. The string consists of one or more SQL statements separated by semicolons. |
Group Replication
Variable name |
Feature description |
|---|---|
| group_replication_allow_local_disjoint_gtids_join | Specifies whether a local transaction on the server can join a group if the group does not have a transaction. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without returning an error. |
| group_replication_allow_local_lower_version_join | Specifies whether a server with a MySQL server version lower than that of other group members is allowed to join the group. Default value:OFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| group_replication_auto_increment_increment | Automatically sets the increment value for the auto-increment column of each member in the replication group, ensuring that the values in the auto-increment columns of all group members are ordered and non-overlapping in a multi-primary mode group. The default value is7.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| group_replication_bootstrap_group | Specifies to use the current server to bootstrap the group. This variable can only be set on one server, and must be set on one of the servers during the initial bootstrap or during a subsequent bootstrap of the group. The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_components_stop_timeout | The timeout period for waiting for each component when group replication is disabled, in seconds. The default value is2.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| group_replication_compression_threshold | The threshold for compressing messages sent between group members. When the number of messages exceeds this threshold, the messages will be compressed. The default value is1000000.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| group_replication_enforce_update_everywhere_checks | Enables or disables strict consistency checking for multi-primary updates at any time. The default value isOFF, which indicates to disable the check.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error message. |
| group_replication_exit_state_action | Sets the behavior of group replication when a server instance detaches from the group due to an exception. The default value isREAD_ONLY.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting takes effect without an error being returned. |
| group_replication_flow_control_applier_threshold | Specifies the number of transactions waiting in the queue of the application that triggers traffic control. The default value is25000.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_flow_control_certifier_threshold | Specifies the number of waiting transactions in the queue of validators that trigger flow control. The default value is25000.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| group_replication_flow_control_mode | Specifies the mode used for flow control. The default value isQUOTA.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| group_replication_force_members | Specify the list of member addresses in the format ofhost1:port1,host2:port2. This variable is used to force the creation of a new group. After successful setting, members that are excluded (members not specified in this variable) will not receive new view messages and will also be blocked (blocking write operations). Its default value is empty.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting does not take effect without an error message. |
| group_replication_group_name | Specifies the group name of the replication group to which the current server belongs. The default value is empty.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| group_replication_group_seeds | Specify the list of addresses for the seed members in the format ofhost1:port1,host2:port2. Its default value is empty.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_gtid_assignment_block_size | Specifies the number of consecutive GTIDs retained for each member. The default value is1000000.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without returning an error. |
| group_replication_ip_whitelist | Specifies which hosts (IP addresses or hostnames) are allowed to connect to the group. The allowed addresses are called allowlist addresses. The default value isAUTOMATIC.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being returned. |
| group_replication_local_address | The group replication member provides the network address for other members in the group to connect and access. Its default value is empty.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_member_weight | Assigns a percentage weight to group members. This weight affects the likelihood of a member being selected as the primary node during a failover (only meaningful for groups in single-primary mode). When the primary node of a group in single-primary mode leaves the group, members with higher weight values are preferentially selected as the new primary node. The default value is50
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_poll_spin_loops | Specifies the number of times the group replication communication thread waits for the communication engine mutex to be released before waiting for more incoming network messages. The default value is0.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| group_replication_recovery_complete_at | Specifies the strategy for caching transactions by the application after status transfer is completed during distributed recovery. Default value:TRANSACTIONS_APPLIED.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_reconnect_interval | When a new server attempts to join a group and cannot find an available donor for distributed recovery for some reason, it will attempt to reconnect to find an available donor. This variable sets the interval for reconnection, in seconds. The default value is60.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_retry_count | When a new server attempts to join a group and cannot find an available donor for distributed recovery for some reason, it will attempt to reconnect to find an available donor. This variable sets the number of reconnection attempts to find an available donor. Its default value is10.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting takes effect without an error being returned. |
| group_replication_recovery_ssl_ca | Specifies the path of the file containing the list of trusted SSL certificate authorities used for distributed restore connections. The default value is empty.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_capath | Specifies the directory path for trusted SSL certificates issued by a certificate authority, used for distributed restore connections. The default value is empty.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_cert | Specifies the name of the SSL certificate file used to establish a secure connection for distributed recovery. The default value is empty.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_cipher | Specifies the list of encryption algorithms allowed for SSL encryption. The available encryption algorithms depend on the version of the SSL library used when compiling MySQL Server, as different SSL libraries support different encryption algorithms. The default value is empty.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_crl | Specifies the filename of the certificate revocation list file. The default value is empty.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_crlpath | Specifies the directory path containing the certificate revocation list file. The default value is empty.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_key | Specifies the name of the SSL key file used to establish a secure connection for distributed recovery. The default value is empty.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_verify_server_cert | Specifies whether to verify the server common name in the donor certificate during distributed recovery. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being returned. |
| group_replication_recovery_use_ssl | Specifies whether to use SSL for the connection channel during distributed recovery for group replication members. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| group_replication_single_primary_mode | Specifies whether group replication runs in single-primary mode and automatically selects a server to handle read/write workloads. If set toONindicates that there is only one readable and writable primary node, and all other group members are standby nodes. If set toOFFindicates that the single-primary mode is disabled, that is, the multi-primary mode is enabled. In multi-primary mode, all group members are typically read-write primary nodes. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting takes effect without an error being returned. |
| group_replication_ssl_mode | Specifies the security status of SSL connections between group replication members. The default value isDISABLED.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_start_on_boot | Specifies whether to enable group replication upon server startup. Default value:OFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| group_replication_transaction_size_limit | Specifies the maximum size of a transaction that can be received within group replication, in bytes. The default value is150000000.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_unreachable_majority_timeout | Specifies the waiting time, in seconds, before a member leaves a group when it encounters a network partition and loses connection to the majority of group members. The default value is0.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
Session Level
Version information
Variable name |
Feature description |
|---|---|
| ob_last_schema_version | Sets the version number of the schema most recently used in the current session. |
| old_alter_table | Specifies whether to enable the legacy ALTER TABLE syntax and operation mode. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
Debugging
Variable name |
Feature description |
|---|---|
| debug | Used to set debugging options. The default value isd:t:i:o,/tmp/mysqld.trace.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
Read/Write and Query
Variable name |
Feature description |
|---|---|
| is_result_accurate | When the query containstopkWhen prompted,is_result_accurateIndicates whether the result is correct. |
| long_query_time | The threshold for identifying slow queries. |
Replica-related
Variable name |
Feature description |
|---|---|
| master_info_repository | Specifies whether metadata is stored as records in the mysql table of the system database InnoDB or as files in the data directory. The default value isFILE.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
Cache-related
Variable name |
Feature description |
|---|---|
| table_definition_cache | Sets the amount of memory space used to cache table definitions. The default value is-1.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| table_open_cache_instances | Specifies the number of instances for opening table cache. The default value is16.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. It can be queried but cannot be set. |
Cluster-related
Variable name |
Feature description |
|---|---|
| ob_capability_flag | It is a capability provided by an OBServer node for capability negotiation when connecting to a proxy, informing the proxy which features the current OBServer node supports and which it does not. |
| ob_proxy_partition_hit | It specifies whether OBProxy sends the data requested by the SQL statement to the OBServer node where the data resides in the primary partition. |
| ob_org_cluster_id | Used to set the for the OceanBase AI Database cluster.CLUSTER_ID. |
NDB storage engine
Variable name |
Feature description |
|---|---|
| ndb_allow_copying_alter_table | Whether to AllowALTER TABLEstatements and other DDL statements for table replication operations. The default value isOFF
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ndb_autoincrement_prefetch_sz | Specifies the number of prefetches for auto-increment columns. This value affects the performance and concurrent access capability of auto-increment columns. Default value:1.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| ndb_blob_read_batch_bytes | Configures the maximum size for batch reading of BLOB data in an NDB cluster, in bytes. The default value is65536.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting takes effect without returning an error. |
| ndb_blob_write_batch_bytes | Configures the maximum size of a batch for writing BLOB data in an NDB cluster. The default value is65536.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| ndb_deferred_constraints | Controls whether to delay constraint checking on tables. The default value is0.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error message. |
| ndb_fully_replicated | Determines whether the new table is fully copied. Default value:OFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| ndb_index_stat_enable | Specifies whether to use the NDB index statistics collection feature. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| ndb_index_stat_option | Specifies the options for generating NDB index statistics. The default value isloop_checkon=1000ms,loop_idle=1000ms,loop_busy=100ms,update_batch=1,read_batch=4,idle_batch=32,check_batch=32,check_delay=1m,delete_batch=8,clean_delay=0,error_batch=4,error_delay=1m,evict_batch=8,evict_delay=1m,cache_limit=32M,cache_lowpct=90
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting takes effect without returning an error. |
| ndb_join_pushdown | Controls whether to enable the connection pushdown optimization feature in the storage engine. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| ndb_log_binlog_index | Controls whether to insert the epoch-to-binlog-position mapping into the ndb_binlog_index table. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without returning an error. |
| ndb_log_exclusive_reads | Determines whether to use an exclusive lock to record primary key reads. Default value:OFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| ndb_row_checksum | Specifies the checksum value of a table row. The value is1When set to yes, the checksum value of each row is calculated and stored. If the value is0When this parameter is set to N/A, table row data verification and detection are not performed. The default value is N/A.1.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ndb_use_exact_count | Specifies whether to force NDB to use the SELECT count(*) record count to accelerate such queries during query plan generation. The default value isOFF.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting takes effect without an error being returned. |
| ndb_use_transactions | Controls whether to enable NDB transaction support. The default value isOFF
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error message. |
| ndbinfo_max_bytes | For testing and debugging only. The default value is0
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| ndbinfo_max_rows | For testing and debugging only. The default value is10.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| ndbinfo_show_hidden | Whether to display in the MySQL client.ndbinfoThe underlying internal table of the database. The default value isOFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| myisam_repair_threads | Specifies the number of concurrent threads for repairing a MyISAM table. The default value is1.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being returned. |
| myisam_sort_buffer_size | Specifies the cache size allocated for sorting MyISAM indexes during a REPAIR TABLE operation or for creating indexes using CREATE INDEX (or ALTER TABLE), in bytes. The default value is8388608.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| myisam_stats_method | Specifies the method by which the server calculates NULL values when collecting statistics on index value distribution for a MyISAM table. The default value isnulls_unequal, which means that NULL values are treated as regular values and handled in the same way as other values.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| myisam_use_mmap | Whether to use memory mapping for reading from and writing to MyISAM tables. Default value:OFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting takes effect without an error message. |
SQL/PL
Variable name |
Feature description |
|---|---|
| have_profiling | Used to detect whether query performance analysis is supported. The default value isNO.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried but cannot be set. |
| profiling | Used to enable or disable statement analysis. The default value is0.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| profiling_history_size | Specifies the number of historical query performance records to retain. The default value is15.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| enable_sql_plan_monitor | Specifies whether the SQL statements of the current session are recorded in SQL Plan Monitor. |
System logs
Variable name |
Feature description |
|---|---|
| ob_enable_show_trace | Specifies whether to use trace logs. |
| tracefile_identifier | Used to add specified content to logs, facilitating filtering and iterative tracking of log lines. |
System servers
Variable name |
Feature description |
|---|---|
| pseudo_slave_mode | Specifies whether to convert the server to slave simulation mode. Default value:OFF.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| pseudo_thread_id | Sets the ID of the session thread. Default value:2147483647
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being returned. |
| rbr_exec_mode | Sets the session thread mode to IDEMPOTENT or STRICT. Default value:STRICT
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being returned. |
| preload_buffer_size | Specifies the cache size in bytes for preloading indexes. The default value is32768
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| read_buffer_size | Specifies the cache size in bytes that can be used during data reading. The default value is131072.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being reported. |
| read_rnd_buffer_size | Specifies the cache size for reading data from a MyISAM table. It is also used for multi-range read optimization for any storage engine, in bytes. The default value is262144.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting will not take effect without an error being returned. |
| keep_files_on_create | When not in useDATA DIRECTORYorINDEX DIRECTORYWhen you use the option to specify the storage location for data files or index files, this variable controls whether the server retains existing files in the corresponding directory when creating a MyISAM table. Its default value isOFF, which means to overwrite the existing file.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| max_heap_table_size | Specifies the maximum size, in bytes, to which a memory table created by the user is allowed to grow. The default value is16777216
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| bulk_insert_buffer_size | Specifies the cache size for batch data insertion, in bytes per thread. The default value is8388608.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported. You can query and set it, but the setting takes effect without returning an error. |
Time zone and date related
Variable name |
Feature description |
|---|---|
| timestamp | TIMESTAMPis a timestamp in seconds. This variable affectsselect now(6)The result. |
Transactions and transaction logs
Variable name |
Feature description |
|---|---|
| ob_proxy_set_trx_executed | Used to specify whether the user sends through OBProxy.START TRANSACTION SyntaxTo the OBServer. |
| ob_trace_info | Used to pass-through trace information, which can ultimately be persisted in the redo log. |
Vector operations
Variable name |
Feature description |
|---|---|
| ob_hnsw_ef_search | This parameter specifies the number of neighbor points searched by the HNSW algorithm in each layer of the graph during vector index queries. |
| ob_ivf_nprobes | Specifies the number of nearest cluster centers to search for in a vector index query. This variable affects the performance and recall rate of IVF queries: a larger value results in higher recall but also longer search time. |
Optimizer-related
Variable name |
Feature description |
|---|---|
| ob_table_access_policy | Controls the optimizer to prefer specific storage formats when generating base table plans. |
| partition_index_dive_limit | Specifies the maximum number of partitions that the optimizer can use for row estimation at the storage layer. |
| range_index_dive_limit | Specifies the maximum number of ranges allowed for row estimation at the storage layer by the optimizer. |
Auto-increment columns
Variable name |
Feature description |
|---|---|
| last_insert_id | Retrieves the value of the auto-increment field from the last insert of the current session. |
Group Replication Related
Variable name |
Feature description |
|---|---|
| group_replication_force_members | Specify the list of member addresses in the format ofhost1:port1,host2:port2. This variable is used to force the creation of a new group. After it is successfully set, members that are excluded (those not specified in this variable) will not receive new view messages and will also be blocked (blocking write operations). Its default value is empty.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting will not take effect without an error message. |
| group_replication_group_name | Specifies the group name of the replication group to which the current server belongs. The default value is empty.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error being reported. |
| group_replication_gtid_assignment_block_size | Specifies the number of consecutive GTIDs retained for each member. The default value is1000000.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; it can be queried and set, but the setting will not take effect without an error being reported. |
| group_replication_ip_whitelist | Specifies which hosts (IP addresses or hostnames) are allowed to connect to the group. The allowed addresses are called allowlist addresses. The default value isAUTOMATIC.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported. You can query and set it, but the setting takes effect without an error being returned. |
| group_replication_local_address | The group replication member provides the network address for other members in the group to connect and access. Its default value is empty.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_ca | Specifies the path of the file containing the list of trusted SSL certificate authorities used for distributed restore connections. The default value is empty.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_capath | Specifies the directory path for trusted SSL certificates issued by a certificate authority, used for distributed restore connections. The default value is empty.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_cert | Specifies the name of the SSL certificate file used to establish a secure connection for distributed recovery. The default value is empty.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_cipher | Specifies the list of encryption algorithms allowed for SSL encryption. The available encryption algorithms depend on the version of the SSL library used when compiling MySQL Server, as different SSL libraries support different encryption algorithms. The default value is empty.
NoteThis variable is only for compatibility with MySQL 5.7. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_crl | Specifies the filename of the certificate revocation list file. The default value is empty.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_crlpath | Specifies the directory path containing the certificate revocation list file. The default value is empty.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |
| group_replication_recovery_ssl_key | The name of the SSL key file used to establish a secure connection for distributed recovery. The default value is empty.
NoteThis variable is for compatibility with MySQL 5.7 only. The related feature is not supported; you can query and set it, but the setting will not take effect without an error message. |