调用DescribeParameterTemplates接口查询数据库集群默认参数的列表。

调试

您可以在OpenAPI Explorer中直接运行该接口,免去您计算签名的困扰。运行成功后,OpenAPI Explorer可以自动生成SDK代码示例。

请求参数

名称 类型 是否必选 示例值 描述
Action String DescribeParameterTemplates

系统规定参数,取值为DescribeParameterTemplates

DBType String MySQL

数据库引擎类型,当前仅支持MySQL

DBVersion String 5.7

数据库版本,取值范围如下:

  • 5.6
  • 5.7
  • 8.0
RegionId String cn-hangzhou

地域ID。

说明 您可以通过DescribeRegions接口查看当前账号下的所有可用地域信息,包括地域ID。

返回数据

名称 类型 示例值 描述
DBType String MySQL

数据库引擎类型。

DBVersion String 5.7

数据库引擎版本。

Engine String POLARDB

数据库引擎。

ParameterCount String 183

参数数量。

Parameters Array of TemplateRecord

参数列表。

TemplateRecord
CheckingCode String [ROW|STATEMENT|MIXED]

参数取值范围。

ForceModify String true

参数是否可修改,取值范围如下:

  • true:可修改
  • false:不可修改
ForceRestart String false

参数修改后,是否需要重启新参数值才生效。取值范围如下:

  • true:需要重启
  • false:不需要重启
ParameterDescription String What form of binary logging the master will use.

参数描述。

ParameterName String binlog_format

参数名称。

ParameterValue String ROW

参数默认值。

RequestId String D963934D-8605-4473-8EAC-54C719******

请求ID。

示例

请求示例

http(s)://polardb.aliyuncs.com/?Action=DescribeParameterTemplates
&DBType=MySQL
&DBVersion=5.7
&RegionId=cn-hangzhou
&<公共请求参数>

正常返回示例

XML格式

<DescribeParameterTemplatesResponse>
  <ParameterCount>183</ParameterCount>
  <Parameters>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>autocommit</ParameterName>
              <ParameterDescription>The autocommit mode. If set to 1, all changes to a table take effect immediately. If set to 0, you must use COMMIT to accept a transaction or ROLLBACK to cancel it. If autocommit is 0 and you change it to 1, MySQL performs an automatic COMMIT of any open transaction.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>automatic_sp_privileges</ParameterName>
              <ParameterDescription>When this variable has a value of 1 (the default), the server automatically grants the EXECUTE and ALTER ROUTINE privileges to the creator of a stored routine, if the user cannot already execute and alter or drop the routine. (The ALTER ROUTINE privilege is required to drop the routine.) The server also automatically drops those privileges from the creator when the routine is dropped. If automatic_sp_privileges is 0, the server does not automatically add or drop these privileges.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-65535]</CheckingCode>
              <ParameterValue>1</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>auto_increment_increment</ParameterName>
              <ParameterDescription>Auto-increment columns are incremented by this</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-65535]</CheckingCode>
              <ParameterValue>1</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>auto_increment_offset</ParameterName>
              <ParameterDescription>Offset added to Auto-increment columns. Used when auto-increment-increment != 1</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-65535]</CheckingCode>
              <ParameterValue>3000</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>back_log</ParameterName>
              <ParameterDescription>The number of outstanding connection requests MySQL can have.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[4096-16777216]</CheckingCode>
              <ParameterValue>2097152</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>binlog_cache_size</ParameterName>
              <ParameterDescription>The size of the transactional cache for updates to transactional engines for the binary log.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[NONE|CRC32]</CheckingCode>
              <ParameterValue>CRC32</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>binlog_checksum</ParameterName>
              <ParameterDescription>When enabled, this variable causes the master to write a checksum for each event in the binary log.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ROW|STATEMENT|MIXED]</CheckingCode>
              <ParameterValue>ROW</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>binlog_format</ParameterName>
              <ParameterDescription>What form of binary logging the master will use.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>binlog_order_commits</ParameterName>
              <ParameterDescription>Issue internal commit calls in the same order as transactions are written to the binary log.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>binlog_rows_query_log_events</ParameterName>
              <ParameterDescription>The binlog_rows_query_log_events system variable affects row-based logging only. When enabled, it causes the MySQL Server to write informational log events such as row query log events into its binary log. This information can be used for debugging and related purposes, such as obtaining the original query issued on the master when it cannot be reconstructed from the row updates.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[full|minimal|noblob]</CheckingCode>
              <ParameterValue>FULL</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>binlog_row_image</ParameterName>
              <ParameterDescription>For MySQL row-based replication, this variable determines how row images are written to the binary log.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[4096-1073741824]</CheckingCode>
              <ParameterValue>32768</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>binlog_stmt_cache_size</ParameterName>
              <ParameterDescription>The size of the statement cache for updates to non-transactional engines for the binary log. If you often use statements updating a great number of rows, you can increase this to get more performance.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[utf8|latin1|gbk|utf8mb4|binary]</CheckingCode>
              <ParameterValue>binary</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>character_set_filesystem</ParameterName>
              <ParameterDescription>The file system character set. This variable is used to interpret string literals that refer to file names, such as in the LOAD DATA INFILE and SELECT ... INTO OUTFILE statements and the LOAD_FILE() function. Such file names are converted from character_set_client to character_set_filesystem before the file opening attempt occurs. The default value is binary, which means that no conversion occurs. For systems on which multibyte file names are permitted, a different value may be more appropriate. For example, if the system represents file names using UTF-8, set character_set_filesystem to "utf8".</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[utf8|latin1|gbk|utf8mb4]</CheckingCode>
              <ParameterValue>utf8</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>character_set_server</ParameterName>
              <ParameterDescription>The server's default character set.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[2-31536000]</CheckingCode>
              <ParameterValue>10</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>connect_timeout</ParameterName>
              <ParameterDescription>The number of seconds that the mysqld server waits for a connect packet before responding with Bad handshake.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[SYSTEM|-12:00|-11:00|-10:00|-9:00|-8:00|-7:00|-6:00|-5:00|-4:00|-3:00|-2:00|-1:00|\+0:00|\+1:00|\+2:00|\+3:00|\+4:00|\+5:00|\+5:30|\+6:00|\+6:30|\+7:00|\+8:00|\+9:00|\+10:00|\+11:00|\+12:00|\+13:00]</CheckingCode>
              <ParameterValue>SYSTEM</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>default_time_zone</ParameterName>
              <ParameterDescription>Set the default server time zone.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[InnoDB|MyISAM]</CheckingCode>
              <ParameterValue>MyISAM</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>default_tmp_storage_engine</ParameterName>
              <ParameterDescription>The default storage engine for new explicit temporary tables.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-7]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>default_week_format</ParameterName>
              <ParameterDescription>The default mode value to use for the WEEK() function.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>disconnect_on_expired_password</ParameterName>
              <ParameterDescription>This variable controls how the server handles clients with expired passwords.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-30]</CheckingCode>
              <ParameterValue>4</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>div_precision_increment</ParameterName>
              <ParameterDescription>This variable indicates the number of digits by which to increase the scale of the result of division operations performed with the / operator.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>end_markers_in_json</ParameterName>
              <ParameterDescription>Whether optimizer JSON output should add end markers.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>10</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>eq_range_index_dive_limit</ParameterName>
              <ParameterDescription>This variable indicates the number of equality ranges in an equality comparison condition when the optimizer should switch from using index dives to index statistics in estimating the number of qualifying rows.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>explicit_defaults_for_timestamp</ParameterName>
              <ParameterDescription>This system variable determines whether the server enables certain nonstandard behaviors for default values and NULL-value handling in TIMESTAMP columns.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>flush_time</ParameterName>
              <ParameterDescription>If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and synchronize unflushed data to disk. This option is best used only on systems with minimal resources.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[4-1073741824]</CheckingCode>
              <ParameterValue>1024</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>group_concat_max_len</ParameterName>
              <ParameterDescription>The maximum permitted result length in bytes for the GROUP_CONCAT() function.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-65536]</CheckingCode>
              <ParameterValue>128</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>host_cache_size</ParameterName>
              <ParameterDescription>The size of the internal host cache (see Section 8.12.5.2, “DNS Lookup Optimization and the Host Cache”). Setting the size to 0 disables the host cache. Changing the cache size at runtime implicitly causes a FLUSH HOSTS operation to clear the host cache and truncate the host_cache table.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_adaptive_flushing</ParameterName>
              <ParameterDescription>Specifies whether to dynamically adjust the rate of flushing dirty pages in the InnoDB buffer pool based on the workload. Adjusting the flush rate dynamically is intended to avoid bursts of I/O activity.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-70]</CheckingCode>
              <ParameterValue>10</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_adaptive_flushing_lwm</ParameterName>
              <ParameterDescription>Defines the low water mark representing percentage of redo log capacity at which adaptive flushing is enabled.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_adaptive_hash_index</ParameterName>
              <ParameterDescription>Enable adaptive hash index.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-512]</CheckingCode>
              <ParameterValue>8</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_adaptive_hash_index_parts</ParameterName>
              <ParameterDescription>Partitions the adaptive hash index search system. Each index is bound to a specific partition, with each partition protected by a separate latch.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-1000000]</CheckingCode>
              <ParameterValue>150000</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_adaptive_max_sleep_delay</ParameterName>
              <ParameterDescription>Permits InnoDB to automatically adjust the value of innodb_thread_sleep_delay up or down according to the current workload. Any nonzero value enables automated, dynamic adjustment of the innodb_thread_sleep_delay value, up to the maximum value specified in the innodb_adaptive_max_sleep_delay option. The value represents the number of microseconds. This option can be useful in busy systems, with greater than 16 InnoDB threads. (In practice, it is most valuable for MySQL systems with hundreds or thousands of simultaneous connections.)</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-2]</CheckingCode>
              <ParameterValue>1</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_autoinc_lock_mode</ParameterName>
              <ParameterDescription>The lock mode to use for generating auto-increment values.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_buffer_pool_dump_at_shutdown</ParameterName>
              <ParameterDescription>Specifies whether to record the pages cached in the InnoDB buffer pool when the MySQL server is shut down, to shorten the warmup process at the next restart. Typically used in combination with innodb_buffer_pool_load_at_startup. The innodb_buffer_pool_dump_pct option defines the percentage of most recently used buffer pool pages to dump.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_buffer_pool_load_at_startup</ParameterName>
              <ParameterDescription>Specifies that, on MySQL server startup, the InnoDB buffer pool is automatically warmed up by loading the same pages it held at an earlier time. Typically used in combination with innodb_buffer_pool_dump_at_shutdown.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[none|inserts|deletes|changes|purges|all]</CheckingCode>
              <ParameterValue>none</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_change_buffering</ParameterName>
              <ParameterDescription>Whether InnoDB performs change buffering, an optimization that delays write operations to secondary indexes so that the I/O operations can be performed sequentially. Permitted values are described in the following table.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-50]</CheckingCode>
              <ParameterValue>25</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_change_buffer_max_size</ParameterName>
              <ParameterDescription>Maximum size for the InnoDB change buffer, as a percentage of the total size of the buffer pool. You might increase this value for a MySQL server with heavy insert, update, and delete activity, or decrease it for a MySQL server with unchanging data used for reporting.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[INNODB|CRC32|STRICT_INNODB|STRICT_CRC32]</CheckingCode>
              <ParameterValue>CRC32</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_checksum_algorithm</ParameterName>
              <ParameterDescription>Specifies how to generate and verify the checksum stored in the disk blocks of InnoDB tablespaces.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_cmp_per_index_enabled</ParameterName>
              <ParameterDescription>Enables per-index compression-related statistics in the INFORMATION_SCHEMA.INNODB_CMP_PER_INDEX table. Because these statistics can be expensive to gather, only enable this option on development, test, or slave instances during performance tuning related to InnoDB compressed tables.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-1000]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_commit_concurrency</ParameterName>
              <ParameterDescription>The number of threads that can commit at the same time. A value of 0 (the default) permits any number of transactions to commit simultaneously.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-100]</CheckingCode>
              <ParameterValue>5</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_compression_failure_threshold_pct</ParameterName>
              <ParameterDescription>Defines the compression failure rate threshold for a table, as a percentage, at which point MySQL begins adding padding within compressed pages to avoid expensive compression failures. When this threshold is passed, MySQL begins to leave additional free space within each new compressed page, dynamically adjusting the amount of free space up to the percentage of page size specified by innodb_compression_pad_pct_max. A value of zero disables the mechanism that monitors compression efficiency and dynamically adjusts the padding amount.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-9]</CheckingCode>
              <ParameterValue>6</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_compression_level</ParameterName>
              <ParameterDescription>Specifies the level of zlib compression to use for InnoDB compressed tables and indexes. A higher value lets you fit more data onto a storage device, at the expense of more CPU overhead during compression. A lower value lets you reduce CPU overhead when storage space is not critical, or you expect the data is not especially compressible.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-75]</CheckingCode>
              <ParameterValue>50</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_compression_pad_pct_max</ParameterName>
              <ParameterDescription>Specifies the maximum percentage that can be reserved as free space within each compressed page, allowing room to reorganize the data and modification log within the page when a compressed table or index is updated and the data might be recompressed. Only applies when innodb_compression_failure_threshold_pct is set to a nonzero value, and the rate of compression failures passes the cutoff point.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-4294967295]</CheckingCode>
              <ParameterValue>5000</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_concurrency_tickets</ParameterName>
              <ParameterDescription>Determines the number of threads that can enter InnoDB concurrently.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_disable_sort_file_cache</ParameterName>
              <ParameterDescription>If ON, disable page cache when innodb using sort file.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0|1|2]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_flush_neighbors</ParameterName>
              <ParameterDescription>Specifies whether flushing a page from the InnoDB buffer pool also flushes other dirty pages in the same extent.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1600000-80000000]</CheckingCode>
              <ParameterValue>8000000</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_ft_cache_size</ParameterName>
              <ParameterDescription>The memory allocated, in bytes, for the InnoDB FULLTEXT search index cache, which holds a parsed document in memory while creating an InnoDB FULLTEXT index. Index inserts and updates are only committed to disk when the innodb_ft_cache_size size limit is reached. innodb_ft_cache_size defines the cache size on a per table basis.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_ft_enable_diag_print</ParameterName>
              <ParameterDescription>Whether to enable additional full-text search (FTS) diagnostic output. This option is primarily intended for advanced FTS debugging and will not be of interest to most users. Output is printed to the error log and includes information.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_ft_enable_stopword</ParameterName>
              <ParameterDescription>Specifies that a set of stopwords is associated with an InnoDB FULLTEXT index at the time the index is created. If the innodb_ft_user_stopword_table option is set, the stopwords are taken from that table. Else, if the innodb_ft_server_stopword_table option is set, the stopwords are taken from that table. Otherwise, a built-in set of default stopwords is used.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[10-84]</CheckingCode>
              <ParameterValue>84</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_ft_max_token_size</ParameterName>
              <ParameterDescription>Maximum character length of words that are stored in an InnoDB FULLTEXT index.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-16]</CheckingCode>
              <ParameterValue>3</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_ft_min_token_size</ParameterName>
              <ParameterDescription>Minimum length of words that are stored in an InnoDB FULLTEXT index.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>2000</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_ft_num_word_optimize</ParameterName>
              <ParameterDescription>Number of words to process during each OPTIMIZE TABLE operation on an InnoDB FULLTEXT index. Because a bulk insert or update operation to a table containing a full-text search index could require substantial index maintenance to incorporate all changes, you might do a series of OPTIMIZE TABLE statements, each picking up where the last left off.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1000000-4294967295]</CheckingCode>
              <ParameterValue>2000000000</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_ft_result_cache_limit</ParameterName>
              <ParameterDescription>The InnoDB full-text search query result cache limit (defined in bytes) per full-text search query or per thread. Intermediate and final InnoDB full-text search query results are handled in memory. Use innodb_ft_result_cache_limit to place a size limit on the full-text search query result cache to avoid excessive memory consumption in case of very large InnoDB full-text search query results (millions or hundreds of millions of rows, for example). Memory is allocated as required when a full-text search query is processed. If the result cache size limit is reached, an error is returned indicating that the query exceeds the maximum allowed memory.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-32]</CheckingCode>
              <ParameterValue>2</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_ft_sort_pll_degree</ParameterName>
              <ParameterDescription>Number of threads used in parallel to index and tokenize text in an InnoDB FULLTEXT index when building a search index.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[32000000-1600000000]</CheckingCode>
              <ParameterValue>640000000</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_ft_total_cache_size</ParameterName>
              <ParameterDescription>The total memory allocated, in bytes, for the InnoDB full-text search index cache for all tables. Creating numerous tables, each with a FULLTEXT search index, could consume a significant portion of available memory. innodb_ft_total_cache_size defines a global memory limit for all full-text search indexes to help avoid excessive memory consumption. If the global limit is reached by an index operation, a forced sync is triggered.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[200-18446744073709551615]</CheckingCode>
              <ParameterValue>4000</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_io_capacity</ParameterName>
              <ParameterDescription>The innodb_io_capacity parameter sets an upper limit on I/O activity performed by InnoDB background tasks, such as flushing pages from the buffer pool and merging data from the change buffer.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[100-4294967295]</CheckingCode>
              <ParameterValue>8000</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_io_capacity_max</ParameterName>
              <ParameterDescription>If flushing activity falls behind, InnoDB can flush more aggressively than the limit imposed by innodb_io_capacity. innodb_io_capacity_max defines an upper limit the number of I/O operations performed per second by InnoDB background tasks in such situations.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_large_prefix</ParameterName>
              <ParameterDescription>Enable this option to allow index key prefixes longer than 767 bytes (up to 3072 bytes) for InnoDB tables that use DYNAMIC or COMPRESSED row format.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-1073741824]</CheckingCode>
              <ParameterValue>50</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_lock_wait_timeout</ParameterName>
              <ParameterDescription>The timeout in seconds an InnoDB transaction may wait for a row lock before giving up. The default value is 50 seconds. Unit:Second.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_log_compressed_pages</ParameterName>
              <ParameterDescription>Specifies whether images of re-compressed pages are written to the redo log. Re-compression may occur when changes are made to compressed data.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[50-90]</CheckingCode>
              <ParameterValue>60</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_max_dirty_pages_pct</ParameterName>
              <ParameterDescription>This is an integer in the range from 0 to 100. The default value is 90 for the built-in InnoDB, 75 for InnoDB Plugin. The main thread in InnoDB tries to write pages from the buffer pool so that the percentage of dirty (not yet written) pages will not exceed this value.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-50]</CheckingCode>
              <ParameterValue>10</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_max_dirty_pages_pct_lwm</ParameterName>
              <ParameterDescription>Defines a low water mark representing the percentage of dirty pages at which preflushing is enabled to control the dirty page ratio.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_max_purge_lag</ParameterName>
              <ParameterDescription>Defines the maximum length of the purge queue. The default value of 0 indicates no limit (no delays).</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_max_purge_lag_delay</ParameterName>
              <ParameterDescription>Specifies the maximum delay in microseconds for the delay imposed by theinnodb_max_purge_lag configuration option. A nonzero value represents an upper limit on the delay period computed from the formula based on the value of innodb_max_purge_lag. The default of zero means that there is no upper limit imposed on the delay interval.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[10485760-107374182400]</CheckingCode>
              <ParameterValue>1073741824</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_max_undo_log_size</ParameterName>
              <ParameterDescription>Defines a threshold size for undo tablespaces. If an undo tablespace exceeds the threshold, it can be marked for truncation when innodb_undo_log_truncate is enabled.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>all</CheckingCode>
              <ParameterValue></ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_monitor_enable</ParameterName>
              <ParameterDescription>Enables InnoDB metrics counters.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[5-95]</CheckingCode>
              <ParameterValue>37</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_old_blocks_pct</ParameterName>
              <ParameterDescription>Specifies the approximate percentage of the InnoDB buffer pool used for the old block sublist.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-1073741824]</CheckingCode>
              <ParameterValue>1000</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_old_blocks_time</ParameterName>
              <ParameterDescription>Non-zero values protect against the buffer pool being filled by data that is referenced only for a brief period, such as during a full table scan.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[65536-21474836480]</CheckingCode>
              <ParameterValue>134217728</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_online_alter_log_max_size</ParameterName>
              <ParameterDescription>Specifies an upper limit in bytes on the size of the temporary log files used during online DDL operations for InnoDB tables.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-8192]</CheckingCode>
              <ParameterValue>3000</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_open_files</ParameterName>
              <ParameterDescription>This variable is relevant only if you use multiple InnoDB tablespaces. It specifies the maximum number of .ibd files that MySQL can keep open at one time. The minimum value is 10. The default value is 300.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_optimize_fulltext_only</ParameterName>
              <ParameterDescription>Changes the way OPTIMIZE TABLE operates on InnoDB tables. Intended to be enabled temporarily, during maintenance operations for InnoDB tables with FULLTEXT indexes.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[OFF|ON]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_print_all_deadlocks</ParameterName>
              <ParameterDescription>Print all deadlocks to MySQL error log (OFF by default).</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-5000]</CheckingCode>
              <ParameterValue>300</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_purge_batch_size</ParameterName>
              <ParameterDescription>Defines the number of undo log pages that purge parses and processes in one batch from the history list.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-128]</CheckingCode>
              <ParameterValue>128</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_purge_rseg_truncate_frequency</ParameterName>
              <ParameterDescription>Defines the frequency with which the purge system frees rollback segments in terms of the number of times that purge is invoked.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-32]</CheckingCode>
              <ParameterValue>4</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_purge_threads</ParameterName>
              <ParameterDescription>The number of background threads devoted to the InnoDB purge operation.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_random_read_ahead</ParameterName>
              <ParameterDescription>Enables the random read-ahead technique for optimizing InnoDB I/O.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-64]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_read_ahead_threshold</ParameterName>
              <ParameterDescription>(InnoDB Plugin only) Controls the sensitivity of linear read-ahead that InnoDB uses to prefetch pages into the buffer pool. If InnoDB reads at least innodb_read_ahead_threshold pages sequentially from an extent (64 pages), it initiates an asynchronous read for the entire following extent.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_rollback_on_timeout</ParameterName>
              <ParameterDescription>InnoDB rolls back only the last statement on a transaction timeout by default.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-128]</CheckingCode>
              <ParameterValue>128</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_rollback_segments</ParameterName>
              <ParameterDescription>Defines the number of rollback segments used by InnoDB.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[65536-67108864]</CheckingCode>
              <ParameterValue>1048576</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_sort_buffer_size</ParameterName>
              <ParameterDescription>Specifies the size of sort buffers used to sort data during creation of an InnoDB index. The specified size defines the amount of data that is read into memory for internal sorting and then written out to disk. This process is referred to as a “run”. During the merge phase, pairs of buffers of the specified size are read in and merged. The larger the setting, the fewer runs and merges there are.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-18446744073709551615]</CheckingCode>
              <ParameterValue>6</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_spin_wait_delay</ParameterName>
              <ParameterDescription>The maximum delay between polls for a spin lock.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_stats_auto_recalc</ParameterName>
              <ParameterDescription>Causes InnoDB to automatically recalculate persistent statistics after the data in a table is changed substantially. The threshold value is 10% of the rows in the table. This setting applies to tables created when the innodb_stats_persistent option is enabled. Automatic statistics recalculation may also be configured by specifying STATS_PERSISTENT=1 in a CREATE TABLE or ALTER TABLE statement. The amount of data sampled to produce the statistics is controlled by the innodb_stats_persistent_sample_pages configuration option.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[nulls_equal|nulls_unequal|nulls_ignored]</CheckingCode>
              <ParameterValue>nulls_equal</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_stats_method</ParameterName>
              <ParameterDescription>How the server treats NULL values when collecting statistics about the distribution of index values for InnoDB tables.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_stats_on_metadata</ParameterName>
              <ParameterDescription>This option only applies when optimizer statistics are configured to be non-persistent.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_stats_persistent</ParameterName>
              <ParameterDescription>Specifies whether InnoDB index statistics are persisted to disk. Otherwise, statistics may be recalculated frequently which can lead to variations in query execution plans. This setting is stored with each table when the table is created. You can set innodb_stats_persistent at the global level before creating a table, or use the STATS_PERSISTENT clause of the CREATE TABLE and ALTER TABLE statements to override the system-wide setting and configure persistent statistics for individual tables.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>20</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_stats_persistent_sample_pages</ParameterName>
              <ParameterDescription>The number of index pages to sample when estimating cardinality and other statistics for an indexed column, such as those calculated by ANALYZE TABLE. Increasing the value improves the accuracy of index statistics, which can improve the query execution plan, at the expense of increased I/O during the execution of ANALYZE TABLE for an InnoDB table.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-1073741824]</CheckingCode>
              <ParameterValue>8</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_stats_transient_sample_pages</ParameterName>
              <ParameterDescription>The number of index pages to sample when estimating cardinality and other statistics for an indexed column, such as those calculated by ANALYZE TABLE.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_status_output</ParameterName>
              <ParameterDescription>Enables or disables periodic output for the standard InnoDB Monitor. Also used in combination with innodb_status_output_locks to enable or disable periodic output for the InnoDB Lock Monitor.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_status_output_locks</ParameterName>
              <ParameterDescription>Enables or disables the InnoDB Lock Monitor. When enabled, the InnoDB Lock Monitor prints additional information about locks in SHOW ENGINE INNODB STATUS output and in periodic output printed to the MySQL error log. Periodic output for the InnoDB Lock Monitor is printed as part of the standard InnoDB Monitor output. The standard InnoDB Monitor must therefore be enabled for the InnoDB Lock Monitor to print data to the MySQL error log periodically.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_strict_mode</ParameterName>
              <ParameterDescription>(InnoDB Plugin only) Whether InnoDB returns errors rather than warnings for certain conditions. This is analogous to strict SQL mode. The default value is OFF. See InnoDB Strict Mode for a list of the conditions that are affected.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_support_xa</ParameterName>
              <ParameterDescription>Enables InnoDB support for two-phase commit in XA transactions, causing an extra disk flush for transaction preparation. The XA mechanism is used internally and is essential for any server that has its binary log turned on and is accepting changes to its data from more than one thread. If you disable innodb_support_xa, transactions can be written to the binary log in a different order than the live database is committing them, which can produce different data when the binary log is replayed in disaster recovery or on a replication slave. Do not disable innodb_support_xa on a replication master server unless you have an unusual setup where only one thread is able to change data.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-1024]</CheckingCode>
              <ParameterValue>16</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>innodb_sync_array_size</ParameterName>
              <ParameterDescription>Splits an internal data structure used to coordinate threads, for higher concurrency in workloads with large numbers of waiting threads. This setting must be configured when the MySQL instance is starting up, and cannot be changed afterward. Increasing the value is recommended for workloads that frequently produce a large number of waiting threads, typically greater than 768.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>30</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_sync_spin_loops</ParameterName>
              <ParameterDescription>The number of times a thread waits for an InnoDB mutex to be freed before the thread is suspended.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_table_locks</ParameterName>
              <ParameterDescription>If autocommit = 0, InnoDB honors LOCK TABLES. MySQL does not return from LOCK TABLES ... WRITE until all other threads have released all their locks to the table. The default value of innodb_table_locks is 1, which means that LOCK TABLES causes InnoDB to lock a table internally if autocommit = 0.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-512]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_thread_concurrency</ParameterName>
              <ParameterDescription>Helps in performance tuning in heavily concurrent environments. Sets the maximum number of threads allowed inside InnoDB. Value 0 will disable the thread throttling.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-1073741824]</CheckingCode>
              <ParameterValue>10000</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_thread_sleep_delay</ParameterName>
              <ParameterDescription>Defines how long InnoDB threads sleep before joining the InnoDB queue, in microseconds.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-128]</CheckingCode>
              <ParameterValue>128</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_undo_logs</ParameterName>
              <ParameterDescription>Defines the number of rollback segments used by InnoDB.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>innodb_undo_log_truncate</ParameterName>
              <ParameterDescription>Enable or disable truncate of UNDO tablespace.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[10-86400]</CheckingCode>
              <ParameterValue>7200</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>interactive_timeout</ParameterName>
              <ParameterDescription>The number of seconds the server waits for activity on an interactive connection before closing it. An interactive client is defined as a client that uses the CLIENT_INTERACTIVE option to mysql_real_connect(). Unit:second.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[InnoDB|MyISAM]</CheckingCode>
              <ParameterValue>MyISAM</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>internal_tmp_disk_storage_engine</ParameterName>
              <ParameterDescription>The default storage engine for on-disk internal tmp table.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ja_JP|pt_BR|en_US]</CheckingCode>
              <ParameterValue>en_US</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>lc_time_names</ParameterName>
              <ParameterDescription>This variable specifies the locale that controls the language used to display day and month names and abbreviations. This variable affects the output from the DATE_FORMAT(), DAYNAME() and MONTHNAME() functions. Locale names are POSIX-style values such as 'ja_JP' or 'pt_BR'. The default value is 'en_US' regardless of your system's locale setting.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-31536000]</CheckingCode>
              <ParameterValue>31536000</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>lock_wait_timeout</ParameterName>
              <ParameterDescription>This variable specifies the timeout in seconds for attempts to acquire metadata locks. The permissible values range from 1 to 31536000 (1 year). The default is 31536000.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>log_bin_trust_function_creators</ParameterName>
              <ParameterDescription>If set to OFF (the default), then when --loose-polar-log-bin is used, creation of a stored function (or trigger) is allowed only to users having the SUPER privilege and only if this stored function (trigger) may not break binary logging. Note that if ALL connections to this server ALWAYS use row-based binary logging, the security issues do not exist and the binary logging cannot break, so you can safely set this to TRUE.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>log_queries_not_using_indexes</ParameterName>
              <ParameterDescription>Whether queries that do not use indexes are logged to the slow query log.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>log_throttle_queries_not_using_indexes</ParameterName>
              <ParameterDescription>If log_queries_not_using_indexes is enabled, the log_throttle_queries_not_using_indexes variable limits the number of such queries per minute that can be written to the slow query log.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0.03-10]</CheckingCode>
              <ParameterValue>1</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>long_query_time</ParameterName>
              <ParameterDescription>If a query takes longer than this many seconds, the server increments the Slow_queries status variable. If the slow query log is enabled, the query is logged to the slow query log file. Unit:Second.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>1209600</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_binlog_expire_logs_seconds</ParameterName>
              <ParameterDescription>If non-zero, binary logs will be purged after loose_binlog_expire_logs_seconds seconds, possible purges happen at startup and at binary log rotation.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-2147483647]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_connection_control_failed_connections_threshold</ParameterName>
              <ParameterDescription>Threshold of connection control for new connections (0 implies disabling the feature, disabled by default).</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-2147483647]</CheckingCode>
              <ParameterValue>2147483647</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_connection_control_max_connection_delay</ParameterName>
              <ParameterDescription>connection control max delay</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-2147483647]</CheckingCode>
              <ParameterValue>1000</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_connection_control_min_connection_delay</ParameterName>
              <ParameterDescription>connection control min delay.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[TRUE|FALSE]</CheckingCode>
              <ParameterValue>FALSE</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_ignore_index_hint_error</ParameterName>
              <ParameterDescription>When this option is enabled, using inexistent index in index hint would be allowed</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-100]</CheckingCode>
              <ParameterValue>8</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_innodb_polar_log_file_max_reuse</ParameterName>
              <ParameterDescription>Max count of purged log files that reserved for reusing.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-31536000]</CheckingCode>
              <ParameterValue>3600</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_innodb_primary_abort_ddl_wait_replica_timeout</ParameterName>
              <ParameterDescription>Primary node will wait at most this many seconds(then transaction will rollback) when it want to make a synchronization point with replica during ddl execution.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_innodb_primary_qcache_invalid_log</ParameterName>
              <ParameterDescription>Log table ids that have been changed by a recently commtted trx. Please turns on this variable on primary node if replica's query_cache_type &gt;= 1.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[4096-268435456]</CheckingCode>
              <ParameterValue>16777216</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_innodb_slave_recv_hash_cells_max</ParameterName>
              <ParameterDescription>Maxinum cells of the hash for storing redo logs.DBA can make it bigger if replica delays too far away, but it will consume more memory in this case.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[4096-268435456]</CheckingCode>
              <ParameterValue>2097152</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_innodb_slave_recv_hash_cells_min</ParameterName>
              <ParameterDescription>Mininal cells of the hash for storing redo logs. DBA can make it bigger if replica delays too far away, but it will consume more memory in this case.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_innodb_slave_show_correct_autoinc</ParameterName>
              <ParameterDescription>Always show correct autoinc value on replica/standby node if enabled.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-1048576]</CheckingCode>
              <ParameterValue>1024</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>loose_max_digest_length</ParameterName>
              <ParameterDescription>Maximum length considered for digest text.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-1073741824]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_max_execution_time</ParameterName>
              <ParameterDescription>Kill SELECT statement that takes over the specified number of milliseconds.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>'.*'</CheckingCode>
              <ParameterValue>''</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_optimizer_switch</ParameterName>
              <ParameterDescription>optimizer_switch=option=val[,option=val...], where option is one of {index_merge, index_merge_union, index_merge_sort_union, index_merge_intersection, engine_condition_pushdown, index_condition_pushdown, mrr, mrr_cost_based, materialization, semijoin, loosescan, firstmatch, duplicateweedout, subquery_materialization_cost_based, skip_scan, block_nested_loop, batched_key_access, use_index_extensions, condition_fanout_filter, derived_merge, join_card_est_using_histogram, limit_offset_pushdown, detach_range_condition } and val is one of{on, off, default}</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>loose_performance_schema</ParameterName>
              <ParameterDescription>Enable the performance schema.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>loose_polar_log_bin</ParameterName>
              <ParameterDescription>Whether the binary log and gtid_mode is enabled.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-31536000]</CheckingCode>
              <ParameterValue>50</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_replica_lock_wait_timeout</ParameterName>
              <ParameterDescription>Timeout in seconds on replica to wait for a lock before returning an error.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_thread_pool_enabled</ParameterName>
              <ParameterDescription>Enable or disable thread pool for new connections (Disabled by default).</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[transactions|statements|none]</CheckingCode>
              <ParameterValue>transactions</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_thread_pool_high_prio_mode</ParameterName>
              <ParameterDescription>In the 'transactions' mode the thread pool uses both high- and low-priority queues depending on whether an event is generated by an already started transaction and whether it has any high priority tickets(see thread_pool_high_prio_tickets). In the 'statements' mode all events(i.e. individual statements) always go to the high priority queue, regardless of the current transaction state and high priority tickets. 'none' is the opposite of 'statements', i.e. disables the high priority queue completely.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>4294967295</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_thread_pool_high_prio_tickets</ParameterName>
              <ParameterDescription>Number of tickets to enter the high priority event queue for each transaction.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-31536000]</CheckingCode>
              <ParameterValue>60</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_thread_pool_idle_timeout</ParameterName>
              <ParameterDescription>Timeout in seconds for an idle thread in the thread pool. Worker thread will be shut down after timeout.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-100000]</CheckingCode>
              <ParameterValue>100000</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_thread_pool_max_threads</ParameterName>
              <ParameterDescription>Maximum allowed number of worker threads in the thread pool.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-1000]</CheckingCode>
              <ParameterValue>20</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_thread_pool_oversubscribe</ParameterName>
              <ParameterDescription>How many additional active worker threads in a group are allowed.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-18446744073709551615]</CheckingCode>
              <ParameterValue>30</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>loose_thread_pool_stall_limit</ParameterName>
              <ParameterDescription>Maximum query execution time in milliseconds, before an executing non-yielding thread is considered stalled. If a worker thread is stalled, additional worker thread may be created to handle remaining clients.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>OFF</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>master_verify_checksum</ParameterName>
              <ParameterDescription>Enabling this variable causes the master to examine checksums when reading from the binary log. master_verify_checksum is disabled by default.in this case, the master uses the event length from the binary log to verify events, so that only complete events are read from the binary log.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[16384-1073741824]</CheckingCode>
              <ParameterValue>1073741824</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>max_allowed_packet</ParameterName>
              <ParameterDescription>The maximum size of one packet or any generated/intermediate string. Unit:Byte.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[4096-18446744073709547520]</CheckingCode>
              <ParameterValue>322122547200</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>max_binlog_stmt_cache_size</ParameterName>
              <ParameterDescription>If nontransactional statements within a transaction require more than this many bytes of memory, the server generates an error. The minimum value is 4096. The maximum and default values are 4GB on 32-bit platforms and 16EB (exabytes) on 64-bit platforms.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-1073741824]</CheckingCode>
              <ParameterValue>100</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>max_connect_errors</ParameterName>
              <ParameterDescription>If more than this many successive connection requests from a host are interrupted without a successful connection, the server blocks that host from further connections.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-65535]</CheckingCode>
              <ParameterValue>64</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>max_error_count</ParameterName>
              <ParameterDescription>The maximum number of error, warning, and information messages to be stored for display by the SHOW ERRORS and SHOW WARNINGS statements. This is the same as the number of condition areas in the diagnostics area, and thus the number of conditions that can be inspected by GET DIAGNOSTICS.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[16384-10737418240]</CheckingCode>
              <ParameterValue>67108864</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>max_heap_table_size</ParameterName>
              <ParameterDescription>This variable sets the maximum size to which user-created MEMORY tables are permitted to grow. The value of the variable is used to calculate MEMORY table MAX_ROWS values. Setting this variable has no effect on any existing MEMORY table, unless the table is re-created with a statement such as CREATE TABLE or altered with ALTER TABLE or TRUNCATE TABLE. A server restart also sets the maximum size of existing MEMORY tables to the global max_heap_table_size value.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[512-18446744073709551615]</CheckingCode>
              <ParameterValue>18446744073709551615</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>max_join_size</ParameterName>
              <ParameterDescription>Do not permit statements that probably need to examine more than max_join_size rows (for single-table statements) or row combinations (for multiple-table statements) or that are likely to do more than max_join_size disk seeks. By setting this value, you can catch statements where keys are not used properly and that would probably take a long time. Set it if your users tend to perform joins that lack a WHERE clause, that take a long time, or that return millions of rows.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[4-8388608]</CheckingCode>
              <ParameterValue>1024</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>max_length_for_sort_data</ParameterName>
              <ParameterDescription>The cutoff on the size of index values that determines which filesort algorithm to use.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-1048576]</CheckingCode>
              <ParameterValue>16382</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>max_prepared_stmt_count</ParameterName>
              <ParameterDescription>This variable limits the total number of prepared statements in the server. The sum of the number of prepared statements across all sessions. The default value is 16,382. The permissible range of values is from 0 to 1 million. Setting the value to 0 disables prepared statements.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-18446744073709551615]</CheckingCode>
              <ParameterValue>18446744073709500000</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>max_seeks_for_key</ParameterName>
              <ParameterDescription>Limit the assumed maximum number of seeks when looking up rows based on a key. The MySQL optimizer assumes that no more than this number of key seeks are required when searching for matching rows in a table by scanning an index, regardless of the actual cardinality of the index. By setting this to a low value (say, 100), you can force MySQL to prefer indexes instead of table scans.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[4-8388608]</CheckingCode>
              <ParameterValue>1024</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>max_sort_length</ParameterName>
              <ParameterDescription>The number of bytes to use when sorting data values. The server uses only the first max_sort_length bytes of each value and ignores the rest. Consequently, values that differ only after the first max_sort_length bytes compare as equal for GROUP BY, ORDER BY, and DISTINCT operations.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-255]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>max_sp_recursion_depth</ParameterName>
              <ParameterDescription>The number of times that any given stored procedure may be called recursively. The default value for this option is 0, which completely disables recursion in stored procedures. The maximum value is 255.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-102400]</CheckingCode>
              <ParameterValue>102400</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>max_write_lock_count</ParameterName>
              <ParameterDescription>After this many write locks, allow some read locks to run in between.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-1048576]</CheckingCode>
              <ParameterValue>1024</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>metadata_locks_cache_size</ParameterName>
              <ParameterDescription>The size of the metadata locks cache. The server uses this cache to avoid creation and destruction of synchronization objects. This is particularly helpful on systems where such operations are expensive, such as Windows XP.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>min_examined_row_limit</ParameterName>
              <ParameterDescription>Queries that examine fewer than this number of rows are not logged to the slow query log.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1024-1048576]</CheckingCode>
              <ParameterValue>16384</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>net_buffer_length</ParameterName>
              <ParameterDescription>Each client thread is associated with a connection buffer and result buffer. Both begin with a size given by net_buffer_length but are dynamically enlarged up to max_allowed_packet bytes as needed. The result buffer shrinks to net_buffer_length after each SQL statement.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-1073741824]</CheckingCode>
              <ParameterValue>30</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>net_read_timeout</ParameterName>
              <ParameterDescription>The number of seconds to wait for more data from a connection before aborting the read.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-1073741824]</CheckingCode>
              <ParameterValue>10</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>net_retry_count</ParameterName>
              <ParameterDescription>If a read or write on a communication port is interrupted, retry this many times before giving up.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-1073741824]</CheckingCode>
              <ParameterValue>60</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>net_write_timeout</ParameterName>
              <ParameterDescription>The number of seconds to wait for a block to be written to a connection before aborting the write.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[TRUE|FALSE]</CheckingCode>
              <ParameterValue>FALSE</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>old-style-user-limits</ParameterName>
              <ParameterDescription>Enable old-style user limits. (Before MySQL 5.0.3, account resource limits were counted separately for each host from which a user connected rather than per account row in the user table.)</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0|1|2]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>old_passwords</ParameterName>
              <ParameterDescription>This variable controls the password hashing method used by the PASSWORD() function. It also influences password hashing performed by CREATE USER and GRANT statements that specify a password using an IDENTIFIED BY clause.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[4000-1000000]</CheckingCode>
              <ParameterValue>655350</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>open_files_limit</ParameterName>
              <ParameterDescription>If this is not 0, then mysqld will use this value to reserve file descriptors to use with setrlimit(). If this value is 0 then mysqld will reserve max_connections*5 or max_connections + table_cache*2 (whichever is larger) number of file descriptors.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0|1]</CheckingCode>
              <ParameterValue>1</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>optimizer_prune_level</ParameterName>
              <ParameterDescription>Controls the heuristics applied during query optimization to prune less-promising partial plans from the optimizer search space. A value of 0 disables heuristics so that the optimizer performs an exhaustive search. A value of 1 causes the optimizer to prune plans based on the number of rows retrieved by intermediate plans.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-62]</CheckingCode>
              <ParameterValue>62</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>optimizer_search_depth</ParameterName>
              <ParameterDescription>The maximum depth of search performed by the query optimizer. Values larger than the number of relations in a query result in better query plans, but take longer to generate an execution plan for a query. Values smaller than the number of relations in a query return an execution plan quicker, but the resulting plan may be far from being optimal. If set to 0, the system automatically picks a reasonable value.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>1</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>optimizer_trace_limit</ParameterName>
              <ParameterDescription>The maximum number of optimizer traces to display.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>16384</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>optimizer_trace_max_mem_size</ParameterName>
              <ParameterDescription>The maximum cumulative size of stored optimizer traces.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-4294967295]</CheckingCode>
              <ParameterValue>-1</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>optimizer_trace_offset</ParameterName>
              <ParameterDescription>The offset of optimizer traces to display.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1024-1073741824]</CheckingCode>
              <ParameterValue>32768</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>preload_buffer_size</ParameterName>
              <ParameterDescription>The size of the buffer that is allocated when preloading indexes.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1024-1073741824]</CheckingCode>
              <ParameterValue>8192</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>query_alloc_block_size</ParameterName>
              <ParameterDescription>The allocation size of memory blocks that are allocated for objects created during statement parsing and execution.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-1073741824]</CheckingCode>
              <ParameterValue>1048576</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>query_cache_limit</ParameterName>
              <ParameterDescription>Do not cache results that are larger than this number of bytes.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[512-4294967295]</CheckingCode>
              <ParameterValue>4096</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>query_cache_min_res_unit</ParameterName>
              <ParameterDescription>The minimum size (in bytes) for blocks allocated by the query cache. The default value is 4096 (4KB).</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[100-1073741824]</CheckingCode>
              <ParameterValue>3145728</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>query_cache_size</ParameterName>
              <ParameterDescription>The amount of memory allocated for caching query results.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-2]</CheckingCode>
              <ParameterValue>0</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>query_cache_type</ParameterName>
              <ParameterDescription>Set the query cache type. Please turns on variable 'loose_innodb_primary_qcache_invalid_log' on primary node if replica's query_cache_type &gt;= 1.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[TRUE|FALSE]</CheckingCode>
              <ParameterValue>FALSE</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>query_cache_wlock_invalidate</ParameterName>
              <ParameterDescription>Normally, when one client acquires a WRITE lock on a MyISAM table, other clients are not blocked from issuing statements that read from the table if the query results are present in the query cache. Setting this variable to 1 causes acquisition of a WRITE lock for a table to invalidate any queries in the query cache that refer to the table. This forces other clients that attempt to access the table to wait while the lock is in effect.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[8192-1073741824]</CheckingCode>
              <ParameterValue>8192</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>query_prealloc_size</ParameterName>
              <ParameterDescription>The size of the persistent buffer used for statement parsing and execution.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[4096-18446744073709551615]</CheckingCode>
              <ParameterValue>4096</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>range_alloc_block_size</ParameterName>
              <ParameterDescription>The size of blocks that are allocated when doing range optimization.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[TRUE|FALSE]</CheckingCode>
              <ParameterValue>FALSE</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>safe-user-create</ParameterName>
              <ParameterDescription>If this option is enabled, a user cannot create new MySQL users by using the GRANT statement unless the user has the INSERT privilege for the mysql.user table or any column in the table. If you want a user to have the ability to create new users that have those privileges that the user has the right to grant, you should grant the user the following privilege.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-1024]</CheckingCode>
              <ParameterValue>2</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>slow_launch_time</ParameterName>
              <ParameterDescription>If creating a thread takes longer than this many seconds, the server increments the Slow_launch_threads status variable.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[ON|OFF]</CheckingCode>
              <ParameterValue>ON</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>slow_query_log</ParameterName>
              <ParameterDescription>Specify the initial slow query log state. With no argument or an argument of 1, the --slow-query-log option enables the log. If omitted or given with an argument of 0, the option disables the log.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>(s*|REAL_AS_FLOAT|PIPES_AS_CONCAT|ANSI_QUOTES|IGNORE_SPACE|ONLY_FULL_GROUP_BY|NO_UNSIGNED_SUBTRACTION|NO_DIR_IN_CREATE|POSTGRESQL|ORACLE|MSSQL|DB2|MAXDB|NO_KEY_OPTIONS|NO_TABLE_OPTIONS|NO_FIELD_OPTIONS|MYSQL323|MYSQL40|ANSI|NO_AUTO_VALUE_ON_ZERO|NO_BACKSLASH_ESCAPES|STRICT_TRANS_TABLES|STRICT_ALL_TABLES|NO_ZERO_IN_DATE|NO_ZERO_DATE|ALLOW_INVALID_DATES|ERROR_FOR_DIVISION_BY_ZERO|TRADITIONAL|HIGH_NOT_PRECEDENCE|NO_ENGINE_SUBSTITUTION|PAD_CHAR_TO_FULL_LENGTH)(,REAL_AS_FLOAT|,PIPES_AS_CONCAT|,ANSI_QUOTES|,IGNORE_SPACE|,ONLY_FULL_GROUP_BY|,NO_UNSIGNED_SUBTRACTION|,NO_DIR_IN_CREATE|,POSTGRESQL|,ORACLE|,MSSQL|,DB2|,MAXDB|,NO_KEY_OPTIONS|,NO_TABLE_OPTIONS|,NO_FIELD_OPTIONS|,MYSQL323|,MYSQL40|,ANSI|,NO_AUTO_VALUE_ON_ZERO|,NO_BACKSLASH_ESCAPES|,STRICT_TRANS_TABLES|,STRICT_ALL_TABLES|,NO_ZERO_IN_DATE|,NO_ZERO_DATE|,ALLOW_INVALID_DATES|,ERROR_FOR_DIVISION_BY_ZERO|,TRADITIONAL|,HIGH_NOT_PRECEDENCE|,NO_ENGINE_SUBSTITUTION|,PAD_CHAR_TO_FULL_LENGTH)*</CheckingCode>
              <ParameterValue>''</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>sql_mode</ParameterName>
              <ParameterDescription>Modes define what SQL syntax MySQL should support and what kind of data validation checks it should perform.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[16-524288]</CheckingCode>
              <ParameterValue>256</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>stored_program_cache</ParameterName>
              <ParameterDescription>Sets a soft upper limit for the number of cached stored routines per connection. The value of this variable is specified in terms of the number of stored routines held in each of the two caches maintained by the MySQL Server for, respectively, stored procedures and stored functions.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[FALSE|TRUE]</CheckingCode>
              <ParameterValue>FALSE</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>sysdate-is-now</ParameterName>
              <ParameterDescription>SYSDATE() by default returns the time at which it executes, not the time at which the statement in which it occurs begins executing. This differs from the behavior of NOW(). This option causes SYSDATE() to be an alias for NOW(). For information about the implications for binary logging and replication.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[400-80480]</CheckingCode>
              <ParameterValue>16384</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>table_definition_cache</ParameterName>
              <ParameterDescription>The number of table definitions (from .frm files) that can be stored in the definition cache. If you use a large number of tables, you can create a large table definition cache to speed up opening of tables. The table definition cache takes less space and does not use file descriptors, unlike the normal table cache. The minimum and default values are both 400.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-524288]</CheckingCode>
              <ParameterValue>16384</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>table_open_cache</ParameterName>
              <ParameterDescription>The number of open tables for all threads. Increasing this value increases the number of file descriptors that mysqld requires. You can check whether you need to increase the table cache by checking the Opened_tables status variable. If the value of Opened_tables is large and you do not use FLUSH TABLES often (which just forces all tables to be closed and reopened), then you should increase the value of the table_open_cache variable.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1-64]</CheckingCode>
              <ParameterValue>32</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>table_open_cache_instances</ParameterName>
              <ParameterDescription>The number of open tables cache instances.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[FALSE|TRUE]</CheckingCode>
              <ParameterValue>TRUE</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>temp-pool</ParameterName>
              <ParameterDescription>This option is ignored except on Linux. On Linux, it causes most temporary files created by the server to use a small set of names, rather than a unique name for each new file. This works around a problem in the Linux kernel dealing with creating many new files with different names. With the old behavior, Linux seems to “leak” memory, because it is being allocated to the directory entry cache rather than to the disk cache.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[0-16384]</CheckingCode>
              <ParameterValue>256</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>thread_cache_size</ParameterName>
              <ParameterDescription>How many threads the server should cache for reuse. When a client disconnects, the client's threads are put in the cache if there are fewer than thread_cache_size threads there. Requests for threads are satisfied by reusing threads taken from the cache if possible, and only when the cache is empty is a new thread created. This variable can be increased to improve performance if you have a lot of new connections. Normally, this does not provide a notable performance improvement if you have a good thread implementation. However, if your server sees hundreds of connections per second you should normally set thread_cache_size high enough so that most new connections use cached threads. By examining the difference between the Connections and Threads_created status variables, you can see how efficient the thread cache is.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[131072-1073741824]</CheckingCode>
              <ParameterValue>262144</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>thread_stack</ParameterName>
              <ParameterDescription>The stack size of each thread.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[262144-10737418240]</CheckingCode>
              <ParameterValue>2097152</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>tmp_table_size</ParameterName>
              <ParameterDescription>The maximum size of internal in-memory temporary tables.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[READ-UNCOMMITTED|READ-COMMITTED|REPEATABLE-READ]</CheckingCode>
              <ParameterValue>READ-COMMITTED</ParameterValue>
              <ForceRestart>true</ForceRestart>
              <ParameterName>transaction-isolation</ParameterName>
              <ParameterDescription>Sets the default transaction isolation level.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1024-4294967295]</CheckingCode>
              <ParameterValue>8192</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>transaction_alloc_block_size</ParameterName>
              <ParameterDescription>The amount in bytes by which to increase a per-transaction memory pool which needs memory. See the description of transaction_prealloc_size.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[1024-4294967295]</CheckingCode>
              <ParameterValue>4096</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>transaction_prealloc_size</ParameterName>
              <ParameterDescription>There is a per-transaction memory pool from which various transaction-related allocations take memory. The initial size of the pool in bytes is transaction_prealloc_size. For every allocation that cannot be satisfied from the pool because it has insufficient memory available, the pool is increased by transaction_alloc_block_size bytes. When the transaction ends, the pool is truncated to transaction_prealloc_size bytes.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[YES|NO]</CheckingCode>
              <ParameterValue>YES</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>updatable_views_with_limit</ParameterName>
              <ParameterDescription>This variable controls whether updates to a view can be made when the view does not contain all columns of the primary key defined in the underlying table, if the update statement contains a LIMIT clause. (Such updates often are generated by GUI tools.) An update is an UPDATE or DELETE statement. Primary key here means a PRIMARY KEY, or a UNIQUE index in which no column can contain NULL.</ParameterDescription>
        </TemplateRecord>
        <TemplateRecord>
              <ForceModify>true</ForceModify>
              <CheckingCode>[60-259200]</CheckingCode>
              <ParameterValue>86400</ParameterValue>
              <ForceRestart>false</ForceRestart>
              <ParameterName>wait_timeout</ParameterName>
              <ParameterDescription>The number of seconds the server waits for activity on a noninteractive connection before closing it.</ParameterDescription>
        </TemplateRecord>
  </Parameters>
  <RequestId>D963934D-8605-4473-8EAC-54C719******</RequestId>
  <Engine>POLARDB</Engine>
</DescribeParameterTemplatesResponse>

JSON格式

{
	"ParameterCount": 183,
	"Parameters": {
		"TemplateRecord": [
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "false",
				"ParameterName": "autocommit",
				"ParameterDescription": "The autocommit mode. If set to 1, all changes to a table take effect immediately. If set to 0, you must use COMMIT to accept a transaction or ROLLBACK to cancel it. If autocommit is 0 and you change it to 1, MySQL performs an automatic COMMIT of any open transaction."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "false",
				"ParameterName": "automatic_sp_privileges",
				"ParameterDescription": "When this variable has a value of 1 (the default), the server automatically grants the EXECUTE and ALTER ROUTINE privileges to the creator of a stored routine, if the user cannot already execute and alter or drop the routine. (The ALTER ROUTINE privilege is required to drop the routine.) The server also automatically drops those privileges from the creator when the routine is dropped. If automatic_sp_privileges is 0, the server does not automatically add or drop these privileges."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-65535]",
				"ParameterValue": "1",
				"ForceRestart": "false",
				"ParameterName": "auto_increment_increment",
				"ParameterDescription": "Auto-increment columns are incremented by this"
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-65535]",
				"ParameterValue": "1",
				"ForceRestart": "false",
				"ParameterName": "auto_increment_offset",
				"ParameterDescription": "Offset added to Auto-increment columns. Used when auto-increment-increment != 1"
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-65535]",
				"ParameterValue": "3000",
				"ForceRestart": "true",
				"ParameterName": "back_log",
				"ParameterDescription": "The number of outstanding connection requests MySQL can have."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[4096-16777216]",
				"ParameterValue": "2097152",
				"ForceRestart": "false",
				"ParameterName": "binlog_cache_size",
				"ParameterDescription": "The size of the transactional cache for updates to transactional engines for the binary log."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[NONE|CRC32]",
				"ParameterValue": "CRC32",
				"ForceRestart": "false",
				"ParameterName": "binlog_checksum",
				"ParameterDescription": "When enabled, this variable causes the master to write a checksum for each event in the binary log."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ROW|STATEMENT|MIXED]",
				"ParameterValue": "ROW",
				"ForceRestart": "false",
				"ParameterName": "binlog_format",
				"ParameterDescription": "What form of binary logging the master will use."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "binlog_order_commits",
				"ParameterDescription": "Issue internal commit calls in the same order as transactions are written to the binary log."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "binlog_rows_query_log_events",
				"ParameterDescription": "The binlog_rows_query_log_events system variable affects row-based logging only. When enabled, it causes the MySQL Server to write informational log events such as row query log events into its binary log. This information can be used for debugging and related purposes, such as obtaining the original query issued on the master when it cannot be reconstructed from the row updates."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[full|minimal|noblob]",
				"ParameterValue": "FULL",
				"ForceRestart": "false",
				"ParameterName": "binlog_row_image",
				"ParameterDescription": "For MySQL row-based replication, this variable determines how row images are written to the binary log."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[4096-1073741824]",
				"ParameterValue": "32768",
				"ForceRestart": "false",
				"ParameterName": "binlog_stmt_cache_size",
				"ParameterDescription": "The size of the statement cache for updates to non-transactional engines for the binary log. If you often use statements updating a great number of rows, you can increase this to get more performance."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[utf8|latin1|gbk|utf8mb4|binary]",
				"ParameterValue": "binary",
				"ForceRestart": "false",
				"ParameterName": "character_set_filesystem",
				"ParameterDescription": "The file system character set. This variable is used to interpret string literals that refer to file names, such as in the LOAD DATA INFILE and SELECT ... INTO OUTFILE statements and the LOAD_FILE() function. Such file names are converted from character_set_client to character_set_filesystem before the file opening attempt occurs. The default value is binary, which means that no conversion occurs. For systems on which multibyte file names are permitted, a different value may be more appropriate. For example, if the system represents file names using UTF-8, set character_set_filesystem to \"utf8\"."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[utf8|latin1|gbk|utf8mb4]",
				"ParameterValue": "utf8",
				"ForceRestart": "true",
				"ParameterName": "character_set_server",
				"ParameterDescription": "The server's default character set."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[2-31536000]",
				"ParameterValue": "10",
				"ForceRestart": "false",
				"ParameterName": "connect_timeout",
				"ParameterDescription": "The number of seconds that the mysqld server waits for a connect packet before responding with Bad handshake."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[SYSTEM|-12:00|-11:00|-10:00|-9:00|-8:00|-7:00|-6:00|-5:00|-4:00|-3:00|-2:00|-1:00|\\+0:00|\\+1:00|\\+2:00|\\+3:00|\\+4:00|\\+5:00|\\+5:30|\\+6:00|\\+6:30|\\+7:00|\\+8:00|\\+9:00|\\+10:00|\\+11:00|\\+12:00|\\+13:00]",
				"ParameterValue": "SYSTEM",
				"ForceRestart": "true",
				"ParameterName": "default_time_zone",
				"ParameterDescription": "Set the default server time zone."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[InnoDB|MyISAM]",
				"ParameterValue": "MyISAM",
				"ForceRestart": "false",
				"ParameterName": "default_tmp_storage_engine",
				"ParameterDescription": "The default storage engine for new explicit temporary tables."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-7]",
				"ParameterValue": "0",
				"ForceRestart": "false",
				"ParameterName": "default_week_format",
				"ParameterDescription": "The default mode value to use for the WEEK() function."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "true",
				"ParameterName": "disconnect_on_expired_password",
				"ParameterDescription": "This variable controls how the server handles clients with expired passwords."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-30]",
				"ParameterValue": "4",
				"ForceRestart": "false",
				"ParameterName": "div_precision_increment",
				"ParameterDescription": "This variable indicates the number of digits by which to increase the scale of the result of division operations performed with the / operator."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "end_markers_in_json",
				"ParameterDescription": "Whether optimizer JSON output should add end markers."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "10",
				"ForceRestart": "false",
				"ParameterName": "eq_range_index_dive_limit",
				"ParameterDescription": "This variable indicates the number of equality ranges in an equality comparison condition when the optimizer should switch from using index dives to index statistics in estimating the number of qualifying rows."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "true",
				"ParameterName": "explicit_defaults_for_timestamp",
				"ParameterDescription": "This system variable determines whether the server enables certain nonstandard behaviors for default values and NULL-value handling in TIMESTAMP columns."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "0",
				"ForceRestart": "false",
				"ParameterName": "flush_time",
				"ParameterDescription": "If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and synchronize unflushed data to disk. This option is best used only on systems with minimal resources."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[4-1073741824]",
				"ParameterValue": "1024",
				"ForceRestart": "false",
				"ParameterName": "group_concat_max_len",
				"ParameterDescription": "The maximum permitted result length in bytes for the GROUP_CONCAT() function."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-65536]",
				"ParameterValue": "128",
				"ForceRestart": "false",
				"ParameterName": "host_cache_size",
				"ParameterDescription": "The size of the internal host cache (see Section 8.12.5.2, “DNS Lookup Optimization and the Host Cache”). Setting the size to 0 disables the host cache. Changing the cache size at runtime implicitly causes a FLUSH HOSTS operation to clear the host cache and truncate the host_cache table."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "false",
				"ParameterName": "innodb_adaptive_flushing",
				"ParameterDescription": "Specifies whether to dynamically adjust the rate of flushing dirty pages in the InnoDB buffer pool based on the workload. Adjusting the flush rate dynamically is intended to avoid bursts of I/O activity."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-70]",
				"ParameterValue": "10",
				"ForceRestart": "false",
				"ParameterName": "innodb_adaptive_flushing_lwm",
				"ParameterDescription": "Defines the low water mark representing percentage of redo log capacity at which adaptive flushing is enabled."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "innodb_adaptive_hash_index",
				"ParameterDescription": "Enable adaptive hash index."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-512]",
				"ParameterValue": "8",
				"ForceRestart": "true",
				"ParameterName": "innodb_adaptive_hash_index_parts",
				"ParameterDescription": "Partitions the adaptive hash index search system. Each index is bound to a specific partition, with each partition protected by a separate latch."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-1000000]",
				"ParameterValue": "150000",
				"ForceRestart": "false",
				"ParameterName": "innodb_adaptive_max_sleep_delay",
				"ParameterDescription": "Permits InnoDB to automatically adjust the value of innodb_thread_sleep_delay up or down according to the current workload. Any nonzero value enables automated, dynamic adjustment of the innodb_thread_sleep_delay value, up to the maximum value specified in the innodb_adaptive_max_sleep_delay option. The value represents the number of microseconds. This option can be useful in busy systems, with greater than 16 InnoDB threads. (In practice, it is most valuable for MySQL systems with hundreds or thousands of simultaneous connections.)"
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-2]",
				"ParameterValue": "1",
				"ForceRestart": "true",
				"ParameterName": "innodb_autoinc_lock_mode",
				"ParameterDescription": "The lock mode to use for generating auto-increment values."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "innodb_buffer_pool_dump_at_shutdown",
				"ParameterDescription": "Specifies whether to record the pages cached in the InnoDB buffer pool when the MySQL server is shut down, to shorten the warmup process at the next restart. Typically used in combination with innodb_buffer_pool_load_at_startup. The innodb_buffer_pool_dump_pct option defines the percentage of most recently used buffer pool pages to dump."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "true",
				"ParameterName": "innodb_buffer_pool_load_at_startup",
				"ParameterDescription": "Specifies that, on MySQL server startup, the InnoDB buffer pool is automatically warmed up by loading the same pages it held at an earlier time. Typically used in combination with innodb_buffer_pool_dump_at_shutdown."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[none|inserts|deletes|changes|purges|all]",
				"ParameterValue": "none",
				"ForceRestart": "false",
				"ParameterName": "innodb_change_buffering",
				"ParameterDescription": "Whether InnoDB performs change buffering, an optimization that delays write operations to secondary indexes so that the I/O operations can be performed sequentially. Permitted values are described in the following table."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-50]",
				"ParameterValue": "25",
				"ForceRestart": "false",
				"ParameterName": "innodb_change_buffer_max_size",
				"ParameterDescription": "Maximum size for the InnoDB change buffer, as a percentage of the total size of the buffer pool. You might increase this value for a MySQL server with heavy insert, update, and delete activity, or decrease it for a MySQL server with unchanging data used for reporting."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[INNODB|CRC32|STRICT_INNODB|STRICT_CRC32]",
				"ParameterValue": "CRC32",
				"ForceRestart": "false",
				"ParameterName": "innodb_checksum_algorithm",
				"ParameterDescription": "Specifies how to generate and verify the checksum stored in the disk blocks of InnoDB tablespaces."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "innodb_cmp_per_index_enabled",
				"ParameterDescription": "Enables per-index compression-related statistics in the INFORMATION_SCHEMA.INNODB_CMP_PER_INDEX table. Because these statistics can be expensive to gather, only enable this option on development, test, or slave instances during performance tuning related to InnoDB compressed tables."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-1000]",
				"ParameterValue": "0",
				"ForceRestart": "true",
				"ParameterName": "innodb_commit_concurrency",
				"ParameterDescription": "The number of threads that can commit at the same time. A value of 0 (the default) permits any number of transactions to commit simultaneously."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-100]",
				"ParameterValue": "5",
				"ForceRestart": "false",
				"ParameterName": "innodb_compression_failure_threshold_pct",
				"ParameterDescription": "Defines the compression failure rate threshold for a table, as a percentage, at which point MySQL begins adding padding within compressed pages to avoid expensive compression failures. When this threshold is passed, MySQL begins to leave additional free space within each new compressed page, dynamically adjusting the amount of free space up to the percentage of page size specified by innodb_compression_pad_pct_max. A value of zero disables the mechanism that monitors compression efficiency and dynamically adjusts the padding amount."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-9]",
				"ParameterValue": "6",
				"ForceRestart": "false",
				"ParameterName": "innodb_compression_level",
				"ParameterDescription": "Specifies the level of zlib compression to use for InnoDB compressed tables and indexes. A higher value lets you fit more data onto a storage device, at the expense of more CPU overhead during compression. A lower value lets you reduce CPU overhead when storage space is not critical, or you expect the data is not especially compressible."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-75]",
				"ParameterValue": "50",
				"ForceRestart": "false",
				"ParameterName": "innodb_compression_pad_pct_max",
				"ParameterDescription": "Specifies the maximum percentage that can be reserved as free space within each compressed page, allowing room to reorganize the data and modification log within the page when a compressed table or index is updated and the data might be recompressed. Only applies when innodb_compression_failure_threshold_pct is set to a nonzero value, and the rate of compression failures passes the cutoff point."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-4294967295]",
				"ParameterValue": "5000",
				"ForceRestart": "false",
				"ParameterName": "innodb_concurrency_tickets",
				"ParameterDescription": "Determines the number of threads that can enter InnoDB concurrently."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "false",
				"ParameterName": "innodb_disable_sort_file_cache",
				"ParameterDescription": "If ON, disable page cache when innodb using sort file."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0|1|2]",
				"ParameterValue": "0",
				"ForceRestart": "false",
				"ParameterName": "innodb_flush_neighbors",
				"ParameterDescription": "Specifies whether flushing a page from the InnoDB buffer pool also flushes other dirty pages in the same extent."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1600000-80000000]",
				"ParameterValue": "8000000",
				"ForceRestart": "true",
				"ParameterName": "innodb_ft_cache_size",
				"ParameterDescription": "The memory allocated, in bytes, for the InnoDB FULLTEXT search index cache, which holds a parsed document in memory while creating an InnoDB FULLTEXT index. Index inserts and updates are only committed to disk when the innodb_ft_cache_size size limit is reached. innodb_ft_cache_size defines the cache size on a per table basis."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "innodb_ft_enable_diag_print",
				"ParameterDescription": "Whether to enable additional full-text search (FTS) diagnostic output. This option is primarily intended for advanced FTS debugging and will not be of interest to most users. Output is printed to the error log and includes information."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "false",
				"ParameterName": "innodb_ft_enable_stopword",
				"ParameterDescription": "Specifies that a set of stopwords is associated with an InnoDB FULLTEXT index at the time the index is created. If the innodb_ft_user_stopword_table option is set, the stopwords are taken from that table. Else, if the innodb_ft_server_stopword_table option is set, the stopwords are taken from that table. Otherwise, a built-in set of default stopwords is used."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[10-84]",
				"ParameterValue": "84",
				"ForceRestart": "true",
				"ParameterName": "innodb_ft_max_token_size",
				"ParameterDescription": "Maximum character length of words that are stored in an InnoDB FULLTEXT index."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-16]",
				"ParameterValue": "3",
				"ForceRestart": "true",
				"ParameterName": "innodb_ft_min_token_size",
				"ParameterDescription": "Minimum length of words that are stored in an InnoDB FULLTEXT index."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "2000",
				"ForceRestart": "false",
				"ParameterName": "innodb_ft_num_word_optimize",
				"ParameterDescription": "Number of words to process during each OPTIMIZE TABLE operation on an InnoDB FULLTEXT index. Because a bulk insert or update operation to a table containing a full-text search index could require substantial index maintenance to incorporate all changes, you might do a series of OPTIMIZE TABLE statements, each picking up where the last left off."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1000000-4294967295]",
				"ParameterValue": "2000000000",
				"ForceRestart": "false",
				"ParameterName": "innodb_ft_result_cache_limit",
				"ParameterDescription": "The InnoDB full-text search query result cache limit (defined in bytes) per full-text search query or per thread. Intermediate and final InnoDB full-text search query results are handled in memory. Use innodb_ft_result_cache_limit to place a size limit on the full-text search query result cache to avoid excessive memory consumption in case of very large InnoDB full-text search query results (millions or hundreds of millions of rows, for example). Memory is allocated as required when a full-text search query is processed. If the result cache size limit is reached, an error is returned indicating that the query exceeds the maximum allowed memory."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-32]",
				"ParameterValue": "2",
				"ForceRestart": "true",
				"ParameterName": "innodb_ft_sort_pll_degree",
				"ParameterDescription": "Number of threads used in parallel to index and tokenize text in an InnoDB FULLTEXT index when building a search index."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[32000000-1600000000]",
				"ParameterValue": "640000000",
				"ForceRestart": "true",
				"ParameterName": "innodb_ft_total_cache_size",
				"ParameterDescription": "The total memory allocated, in bytes, for the InnoDB full-text search index cache for all tables. Creating numerous tables, each with a FULLTEXT search index, could consume a significant portion of available memory. innodb_ft_total_cache_size defines a global memory limit for all full-text search indexes to help avoid excessive memory consumption. If the global limit is reached by an index operation, a forced sync is triggered."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[200-18446744073709551615]",
				"ParameterValue": "4000",
				"ForceRestart": "false",
				"ParameterName": "innodb_io_capacity",
				"ParameterDescription": "The innodb_io_capacity parameter sets an upper limit on I/O activity performed by InnoDB background tasks, such as flushing pages from the buffer pool and merging data from the change buffer."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[100-4294967295]",
				"ParameterValue": "8000",
				"ForceRestart": "false",
				"ParameterName": "innodb_io_capacity_max",
				"ParameterDescription": "If flushing activity falls behind, InnoDB can flush more aggressively than the limit imposed by innodb_io_capacity. innodb_io_capacity_max defines an upper limit the number of I/O operations performed per second by InnoDB background tasks in such situations."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "false",
				"ParameterName": "innodb_large_prefix",
				"ParameterDescription": "Enable this option to allow index key prefixes longer than 767 bytes (up to 3072 bytes) for InnoDB tables that use DYNAMIC or COMPRESSED row format."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-1073741824]",
				"ParameterValue": "50",
				"ForceRestart": "false",
				"ParameterName": "innodb_lock_wait_timeout",
				"ParameterDescription": "The timeout in seconds an InnoDB transaction may wait for a row lock before giving up. The default value is 50 seconds. Unit:Second."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "innodb_log_compressed_pages",
				"ParameterDescription": "Specifies whether images of re-compressed pages are written to the redo log. Re-compression may occur when changes are made to compressed data."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[50-90]",
				"ParameterValue": "60",
				"ForceRestart": "false",
				"ParameterName": "innodb_max_dirty_pages_pct",
				"ParameterDescription": "This is an integer in the range from 0 to 100. The default value is 90 for the built-in InnoDB, 75 for InnoDB Plugin. The main thread in InnoDB tries to write pages from the buffer pool so that the percentage of dirty (not yet written) pages will not exceed this value."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-50]",
				"ParameterValue": "10",
				"ForceRestart": "false",
				"ParameterName": "innodb_max_dirty_pages_pct_lwm",
				"ParameterDescription": "Defines a low water mark representing the percentage of dirty pages at which preflushing is enabled to control the dirty page ratio."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "0",
				"ForceRestart": "false",
				"ParameterName": "innodb_max_purge_lag",
				"ParameterDescription": "Defines the maximum length of the purge queue. The default value of 0 indicates no limit (no delays)."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "0",
				"ForceRestart": "false",
				"ParameterName": "innodb_max_purge_lag_delay",
				"ParameterDescription": "Specifies the maximum delay in microseconds for the delay imposed by theinnodb_max_purge_lag configuration option. A nonzero value represents an upper limit on the delay period computed from the formula based on the value of innodb_max_purge_lag. The default of zero means that there is no upper limit imposed on the delay interval."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[10485760-107374182400]",
				"ParameterValue": "1073741824",
				"ForceRestart": "false",
				"ParameterName": "innodb_max_undo_log_size",
				"ParameterDescription": "Defines a threshold size for undo tablespaces. If an undo tablespace exceeds the threshold, it can be marked for truncation when innodb_undo_log_truncate is enabled."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "all",
				"ParameterValue": "",
				"ForceRestart": "false",
				"ParameterName": "innodb_monitor_enable",
				"ParameterDescription": "Enables InnoDB metrics counters."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[5-95]",
				"ParameterValue": "37",
				"ForceRestart": "false",
				"ParameterName": "innodb_old_blocks_pct",
				"ParameterDescription": "Specifies the approximate percentage of the InnoDB buffer pool used for the old block sublist."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-1073741824]",
				"ParameterValue": "1000",
				"ForceRestart": "false",
				"ParameterName": "innodb_old_blocks_time",
				"ParameterDescription": "Non-zero values protect against the buffer pool being filled by data that is referenced only for a brief period, such as during a full table scan."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[65536-21474836480]",
				"ParameterValue": "134217728",
				"ForceRestart": "false",
				"ParameterName": "innodb_online_alter_log_max_size",
				"ParameterDescription": "Specifies an upper limit in bytes on the size of the temporary log files used during online DDL operations for InnoDB tables."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-8192]",
				"ParameterValue": "3000",
				"ForceRestart": "true",
				"ParameterName": "innodb_open_files",
				"ParameterDescription": "This variable is relevant only if you use multiple InnoDB tablespaces. It specifies the maximum number of .ibd files that MySQL can keep open at one time. The minimum value is 10. The default value is 300."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "innodb_optimize_fulltext_only",
				"ParameterDescription": "Changes the way OPTIMIZE TABLE operates on InnoDB tables. Intended to be enabled temporarily, during maintenance operations for InnoDB tables with FULLTEXT indexes."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[OFF|ON]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "innodb_print_all_deadlocks",
				"ParameterDescription": "Print all deadlocks to MySQL error log (OFF by default)."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-5000]",
				"ParameterValue": "300",
				"ForceRestart": "false",
				"ParameterName": "innodb_purge_batch_size",
				"ParameterDescription": "Defines the number of undo log pages that purge parses and processes in one batch from the history list."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-128]",
				"ParameterValue": "128",
				"ForceRestart": "false",
				"ParameterName": "innodb_purge_rseg_truncate_frequency",
				"ParameterDescription": "Defines the frequency with which the purge system frees rollback segments in terms of the number of times that purge is invoked."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-32]",
				"ParameterValue": "4",
				"ForceRestart": "true",
				"ParameterName": "innodb_purge_threads",
				"ParameterDescription": "The number of background threads devoted to the InnoDB purge operation."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "innodb_random_read_ahead",
				"ParameterDescription": "Enables the random read-ahead technique for optimizing InnoDB I/O."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-64]",
				"ParameterValue": "0",
				"ForceRestart": "false",
				"ParameterName": "innodb_read_ahead_threshold",
				"ParameterDescription": "(InnoDB Plugin only) Controls the sensitivity of linear read-ahead that InnoDB uses to prefetch pages into the buffer pool. If InnoDB reads at least innodb_read_ahead_threshold pages sequentially from an extent (64 pages), it initiates an asynchronous read for the entire following extent."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "true",
				"ParameterName": "innodb_rollback_on_timeout",
				"ParameterDescription": "InnoDB rolls back only the last statement on a transaction timeout by default."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-128]",
				"ParameterValue": "128",
				"ForceRestart": "false",
				"ParameterName": "innodb_rollback_segments",
				"ParameterDescription": "Defines the number of rollback segments used by InnoDB."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[65536-67108864]",
				"ParameterValue": "1048576",
				"ForceRestart": "true",
				"ParameterName": "innodb_sort_buffer_size",
				"ParameterDescription": "Specifies the size of sort buffers used to sort data during creation of an InnoDB index. The specified size defines the amount of data that is read into memory for internal sorting and then written out to disk. This process is referred to as a “run”. During the merge phase, pairs of buffers of the specified size are read in and merged. The larger the setting, the fewer runs and merges there are."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-18446744073709551615]",
				"ParameterValue": "6",
				"ForceRestart": "false",
				"ParameterName": "innodb_spin_wait_delay",
				"ParameterDescription": "The maximum delay between polls for a spin lock."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "false",
				"ParameterName": "innodb_stats_auto_recalc",
				"ParameterDescription": "Causes InnoDB to automatically recalculate persistent statistics after the data in a table is changed substantially. The threshold value is 10% of the rows in the table. This setting applies to tables created when the innodb_stats_persistent option is enabled. Automatic statistics recalculation may also be configured by specifying STATS_PERSISTENT=1 in a CREATE TABLE or ALTER TABLE statement. The amount of data sampled to produce the statistics is controlled by the innodb_stats_persistent_sample_pages configuration option."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[nulls_equal|nulls_unequal|nulls_ignored]",
				"ParameterValue": "nulls_equal",
				"ForceRestart": "false",
				"ParameterName": "innodb_stats_method",
				"ParameterDescription": "How the server treats NULL values when collecting statistics about the distribution of index values for InnoDB tables."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "innodb_stats_on_metadata",
				"ParameterDescription": "This option only applies when optimizer statistics are configured to be non-persistent."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "false",
				"ParameterName": "innodb_stats_persistent",
				"ParameterDescription": "Specifies whether InnoDB index statistics are persisted to disk. Otherwise, statistics may be recalculated frequently which can lead to variations in query execution plans. This setting is stored with each table when the table is created. You can set innodb_stats_persistent at the global level before creating a table, or use the STATS_PERSISTENT clause of the CREATE TABLE and ALTER TABLE statements to override the system-wide setting and configure persistent statistics for individual tables."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "20",
				"ForceRestart": "false",
				"ParameterName": "innodb_stats_persistent_sample_pages",
				"ParameterDescription": "The number of index pages to sample when estimating cardinality and other statistics for an indexed column, such as those calculated by ANALYZE TABLE. Increasing the value improves the accuracy of index statistics, which can improve the query execution plan, at the expense of increased I/O during the execution of ANALYZE TABLE for an InnoDB table."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-1073741824]",
				"ParameterValue": "8",
				"ForceRestart": "false",
				"ParameterName": "innodb_stats_transient_sample_pages",
				"ParameterDescription": "The number of index pages to sample when estimating cardinality and other statistics for an indexed column, such as those calculated by ANALYZE TABLE."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "innodb_status_output",
				"ParameterDescription": "Enables or disables periodic output for the standard InnoDB Monitor. Also used in combination with innodb_status_output_locks to enable or disable periodic output for the InnoDB Lock Monitor."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "innodb_status_output_locks",
				"ParameterDescription": "Enables or disables the InnoDB Lock Monitor. When enabled, the InnoDB Lock Monitor prints additional information about locks in SHOW ENGINE INNODB STATUS output and in periodic output printed to the MySQL error log. Periodic output for the InnoDB Lock Monitor is printed as part of the standard InnoDB Monitor output. The standard InnoDB Monitor must therefore be enabled for the InnoDB Lock Monitor to print data to the MySQL error log periodically."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "false",
				"ParameterName": "innodb_strict_mode",
				"ParameterDescription": "(InnoDB Plugin only) Whether InnoDB returns errors rather than warnings for certain conditions. This is analogous to strict SQL mode. The default value is OFF. See InnoDB Strict Mode for a list of the conditions that are affected."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "false",
				"ParameterName": "innodb_support_xa",
				"ParameterDescription": "Enables InnoDB support for two-phase commit in XA transactions, causing an extra disk flush for transaction preparation. The XA mechanism is used internally and is essential for any server that has its binary log turned on and is accepting changes to its data from more than one thread. If you disable innodb_support_xa, transactions can be written to the binary log in a different order than the live database is committing them, which can produce different data when the binary log is replayed in disaster recovery or on a replication slave. Do not disable innodb_support_xa on a replication master server unless you have an unusual setup where only one thread is able to change data."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-1024]",
				"ParameterValue": "16",
				"ForceRestart": "true",
				"ParameterName": "innodb_sync_array_size",
				"ParameterDescription": "Splits an internal data structure used to coordinate threads, for higher concurrency in workloads with large numbers of waiting threads. This setting must be configured when the MySQL instance is starting up, and cannot be changed afterward. Increasing the value is recommended for workloads that frequently produce a large number of waiting threads, typically greater than 768."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "30",
				"ForceRestart": "false",
				"ParameterName": "innodb_sync_spin_loops",
				"ParameterDescription": "The number of times a thread waits for an InnoDB mutex to be freed before the thread is suspended."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "false",
				"ParameterName": "innodb_table_locks",
				"ParameterDescription": "If autocommit = 0, InnoDB honors LOCK TABLES. MySQL does not return from LOCK TABLES ... WRITE until all other threads have released all their locks to the table. The default value of innodb_table_locks is 1, which means that LOCK TABLES causes InnoDB to lock a table internally if autocommit = 0."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-512]",
				"ParameterValue": "0",
				"ForceRestart": "false",
				"ParameterName": "innodb_thread_concurrency",
				"ParameterDescription": "Helps in performance tuning in heavily concurrent environments. Sets the maximum number of threads allowed inside InnoDB. Value 0 will disable the thread throttling."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-1073741824]",
				"ParameterValue": "10000",
				"ForceRestart": "false",
				"ParameterName": "innodb_thread_sleep_delay",
				"ParameterDescription": "Defines how long InnoDB threads sleep before joining the InnoDB queue, in microseconds."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-128]",
				"ParameterValue": "128",
				"ForceRestart": "false",
				"ParameterName": "innodb_undo_logs",
				"ParameterDescription": "Defines the number of rollback segments used by InnoDB."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "innodb_undo_log_truncate",
				"ParameterDescription": "Enable or disable truncate of UNDO tablespace."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[10-86400]",
				"ParameterValue": "7200",
				"ForceRestart": "false",
				"ParameterName": "interactive_timeout",
				"ParameterDescription": "The number of seconds the server waits for activity on an interactive connection before closing it. An interactive client is defined as a client that uses the CLIENT_INTERACTIVE option to mysql_real_connect(). Unit:second."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[InnoDB|MyISAM]",
				"ParameterValue": "MyISAM",
				"ForceRestart": "false",
				"ParameterName": "internal_tmp_disk_storage_engine",
				"ParameterDescription": "The default storage engine for on-disk internal tmp table."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ja_JP|pt_BR|en_US]",
				"ParameterValue": "en_US",
				"ForceRestart": "false",
				"ParameterName": "lc_time_names",
				"ParameterDescription": "This variable specifies the locale that controls the language used to display day and month names and abbreviations. This variable affects the output from the DATE_FORMAT(), DAYNAME() and MONTHNAME() functions. Locale names are POSIX-style values such as 'ja_JP' or 'pt_BR'. The default value is 'en_US' regardless of your system's locale setting."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-31536000]",
				"ParameterValue": "31536000",
				"ForceRestart": "false",
				"ParameterName": "lock_wait_timeout",
				"ParameterDescription": "This variable specifies the timeout in seconds for attempts to acquire metadata locks. The permissible values range from 1 to 31536000 (1 year). The default is 31536000."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "false",
				"ParameterName": "log_bin_trust_function_creators",
				"ParameterDescription": "If set to OFF (the default), then when --loose-polar-log-bin is used, creation of a stored function (or trigger) is allowed only to users having the SUPER privilege and only if this stored function (trigger) may not break binary logging. Note that if ALL connections to this server ALWAYS use row-based binary logging, the security issues do not exist and the binary logging cannot break, so you can safely set this to TRUE."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "log_queries_not_using_indexes",
				"ParameterDescription": "Whether queries that do not use indexes are logged to the slow query log."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "0",
				"ForceRestart": "false",
				"ParameterName": "log_throttle_queries_not_using_indexes",
				"ParameterDescription": "If log_queries_not_using_indexes is enabled, the log_throttle_queries_not_using_indexes variable limits the number of such queries per minute that can be written to the slow query log."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0.03-10]",
				"ParameterValue": "1",
				"ForceRestart": "false",
				"ParameterName": "long_query_time",
				"ParameterDescription": "If a query takes longer than this many seconds, the server increments the Slow_queries status variable. If the slow query log is enabled, the query is logged to the slow query log file. Unit:Second."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "1209600",
				"ForceRestart": "false",
				"ParameterName": "loose_binlog_expire_logs_seconds",
				"ParameterDescription": "If non-zero, binary logs will be purged after loose_binlog_expire_logs_seconds seconds, possible purges happen at startup and at binary log rotation."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-2147483647]",
				"ParameterValue": "0",
				"ForceRestart": "false",
				"ParameterName": "loose_connection_control_failed_connections_threshold",
				"ParameterDescription": "Threshold of connection control for new connections (0 implies disabling the feature, disabled by default)."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-2147483647]",
				"ParameterValue": "2147483647",
				"ForceRestart": "false",
				"ParameterName": "loose_connection_control_max_connection_delay",
				"ParameterDescription": "connection control max delay"
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-2147483647]",
				"ParameterValue": "1000",
				"ForceRestart": "false",
				"ParameterName": "loose_connection_control_min_connection_delay",
				"ParameterDescription": "connection control min delay."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[TRUE|FALSE]",
				"ParameterValue": "FALSE",
				"ForceRestart": "false",
				"ParameterName": "loose_ignore_index_hint_error",
				"ParameterDescription": "When this option is enabled, using inexistent index in index hint would be allowed"
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-100]",
				"ParameterValue": "8",
				"ForceRestart": "false",
				"ParameterName": "loose_innodb_polar_log_file_max_reuse",
				"ParameterDescription": "Max count of purged log files that reserved for reusing."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-31536000]",
				"ParameterValue": "3600",
				"ForceRestart": "false",
				"ParameterName": "loose_innodb_primary_abort_ddl_wait_replica_timeout",
				"ParameterDescription": "Primary node will wait at most this many seconds(then transaction will rollback) when it want to make a synchronization point with replica during ddl execution."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "loose_innodb_primary_qcache_invalid_log",
				"ParameterDescription": "Log table ids that have been changed by a recently commtted trx. Please turns on this variable on primary node if replica's query_cache_type >= 1."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[4096-268435456]",
				"ParameterValue": "16777216",
				"ForceRestart": "false",
				"ParameterName": "loose_innodb_slave_recv_hash_cells_max",
				"ParameterDescription": "Maxinum cells of the hash for storing redo logs.DBA can make it bigger if replica delays too far away, but it will consume more memory in this case."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[4096-268435456]",
				"ParameterValue": "2097152",
				"ForceRestart": "false",
				"ParameterName": "loose_innodb_slave_recv_hash_cells_min",
				"ParameterDescription": "Mininal cells of the hash for storing redo logs. DBA can make it bigger if replica delays too far away, but it will consume more memory in this case."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "loose_innodb_slave_show_correct_autoinc",
				"ParameterDescription": "Always show correct autoinc value on replica/standby node if enabled."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-1048576]",
				"ParameterValue": "1024",
				"ForceRestart": "true",
				"ParameterName": "loose_max_digest_length",
				"ParameterDescription": "Maximum length considered for digest text."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-1073741824]",
				"ParameterValue": "0",
				"ForceRestart": "false",
				"ParameterName": "loose_max_execution_time",
				"ParameterDescription": "Kill SELECT statement that takes over the specified number of milliseconds."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "'.*'",
				"ParameterValue": "''",
				"ForceRestart": "false",
				"ParameterName": "loose_optimizer_switch",
				"ParameterDescription": "optimizer_switch=option=val[,option=val...], where option is one of {index_merge, index_merge_union, index_merge_sort_union, index_merge_intersection, engine_condition_pushdown, index_condition_pushdown, mrr, mrr_cost_based, materialization, semijoin, loosescan, firstmatch, duplicateweedout, subquery_materialization_cost_based, skip_scan, block_nested_loop, batched_key_access, use_index_extensions, condition_fanout_filter, derived_merge, join_card_est_using_histogram, limit_offset_pushdown, detach_range_condition } and val is one of{on, off, default}"
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "true",
				"ParameterName": "loose_performance_schema",
				"ParameterDescription": "Enable the performance schema."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "true",
				"ParameterName": "loose_polar_log_bin",
				"ParameterDescription": "Whether the binary log and gtid_mode is enabled."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-31536000]",
				"ParameterValue": "50",
				"ForceRestart": "false",
				"ParameterName": "loose_replica_lock_wait_timeout",
				"ParameterDescription": "Timeout in seconds on replica to wait for a lock before returning an error."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "loose_thread_pool_enabled",
				"ParameterDescription": "Enable or disable thread pool for new connections (Disabled by default)."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[transactions|statements|none]",
				"ParameterValue": "transactions",
				"ForceRestart": "false",
				"ParameterName": "loose_thread_pool_high_prio_mode",
				"ParameterDescription": "In the 'transactions' mode the thread pool uses both high- and low-priority queues depending on whether an event is generated by an already started transaction and whether it has any high priority tickets(see thread_pool_high_prio_tickets). In the 'statements' mode all events(i.e. individual statements) always go to the high priority queue, regardless of the current transaction state and high priority tickets. 'none' is the opposite of 'statements', i.e. disables the high priority queue completely."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "4294967295",
				"ForceRestart": "false",
				"ParameterName": "loose_thread_pool_high_prio_tickets",
				"ParameterDescription": "Number of tickets to enter the high priority event queue for each transaction."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-31536000]",
				"ParameterValue": "60",
				"ForceRestart": "false",
				"ParameterName": "loose_thread_pool_idle_timeout",
				"ParameterDescription": "Timeout in seconds for an idle thread in the thread pool. Worker thread will be shut down after timeout."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-100000]",
				"ParameterValue": "100000",
				"ForceRestart": "false",
				"ParameterName": "loose_thread_pool_max_threads",
				"ParameterDescription": "Maximum allowed number of worker threads in the thread pool."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-1000]",
				"ParameterValue": "20",
				"ForceRestart": "false",
				"ParameterName": "loose_thread_pool_oversubscribe",
				"ParameterDescription": "How many additional active worker threads in a group are allowed."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-18446744073709551615]",
				"ParameterValue": "30",
				"ForceRestart": "false",
				"ParameterName": "loose_thread_pool_stall_limit",
				"ParameterDescription": "Maximum query execution time in milliseconds, before an executing non-yielding thread is considered stalled. If a worker thread is stalled, additional worker thread may be created to handle remaining clients."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "OFF",
				"ForceRestart": "false",
				"ParameterName": "master_verify_checksum",
				"ParameterDescription": "Enabling this variable causes the master to examine checksums when reading from the binary log. master_verify_checksum is disabled by default.in this case, the master uses the event length from the binary log to verify events, so that only complete events are read from the binary log."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[16384-1073741824]",
				"ParameterValue": "1073741824",
				"ForceRestart": "false",
				"ParameterName": "max_allowed_packet",
				"ParameterDescription": "The maximum size of one packet or any generated/intermediate string. Unit:Byte."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[4096-18446744073709547520]",
				"ParameterValue": "322122547200",
				"ForceRestart": "false",
				"ParameterName": "max_binlog_stmt_cache_size",
				"ParameterDescription": "If nontransactional statements within a transaction require more than this many bytes of memory, the server generates an error. The minimum value is 4096. The maximum and default values are 4GB on 32-bit platforms and 16EB (exabytes) on 64-bit platforms."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-1073741824]",
				"ParameterValue": "100",
				"ForceRestart": "false",
				"ParameterName": "max_connect_errors",
				"ParameterDescription": "If more than this many successive connection requests from a host are interrupted without a successful connection, the server blocks that host from further connections."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-65535]",
				"ParameterValue": "64",
				"ForceRestart": "false",
				"ParameterName": "max_error_count",
				"ParameterDescription": "The maximum number of error, warning, and information messages to be stored for display by the SHOW ERRORS and SHOW WARNINGS statements. This is the same as the number of condition areas in the diagnostics area, and thus the number of conditions that can be inspected by GET DIAGNOSTICS."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[16384-10737418240]",
				"ParameterValue": "67108864",
				"ForceRestart": "false",
				"ParameterName": "max_heap_table_size",
				"ParameterDescription": "This variable sets the maximum size to which user-created MEMORY tables are permitted to grow. The value of the variable is used to calculate MEMORY table MAX_ROWS values. Setting this variable has no effect on any existing MEMORY table, unless the table is re-created with a statement such as CREATE TABLE or altered with ALTER TABLE or TRUNCATE TABLE. A server restart also sets the maximum size of existing MEMORY tables to the global max_heap_table_size value."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[512-18446744073709551615]",
				"ParameterValue": "18446744073709551615",
				"ForceRestart": "false",
				"ParameterName": "max_join_size",
				"ParameterDescription": "Do not permit statements that probably need to examine more than max_join_size rows (for single-table statements) or row combinations (for multiple-table statements) or that are likely to do more than max_join_size disk seeks. By setting this value, you can catch statements where keys are not used properly and that would probably take a long time. Set it if your users tend to perform joins that lack a WHERE clause, that take a long time, or that return millions of rows."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[4-8388608]",
				"ParameterValue": "1024",
				"ForceRestart": "false",
				"ParameterName": "max_length_for_sort_data",
				"ParameterDescription": "The cutoff on the size of index values that determines which filesort algorithm to use."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-1048576]",
				"ParameterValue": "16382",
				"ForceRestart": "false",
				"ParameterName": "max_prepared_stmt_count",
				"ParameterDescription": "This variable limits the total number of prepared statements in the server. The sum of the number of prepared statements across all sessions. The default value is 16,382. The permissible range of values is from 0 to 1 million. Setting the value to 0 disables prepared statements."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-18446744073709551615]",
				"ParameterValue": "18446744073709500000",
				"ForceRestart": "false",
				"ParameterName": "max_seeks_for_key",
				"ParameterDescription": "Limit the assumed maximum number of seeks when looking up rows based on a key. The MySQL optimizer assumes that no more than this number of key seeks are required when searching for matching rows in a table by scanning an index, regardless of the actual cardinality of the index. By setting this to a low value (say, 100), you can force MySQL to prefer indexes instead of table scans."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[4-8388608]",
				"ParameterValue": "1024",
				"ForceRestart": "false",
				"ParameterName": "max_sort_length",
				"ParameterDescription": "The number of bytes to use when sorting data values. The server uses only the first max_sort_length bytes of each value and ignores the rest. Consequently, values that differ only after the first max_sort_length bytes compare as equal for GROUP BY, ORDER BY, and DISTINCT operations."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-255]",
				"ParameterValue": "0",
				"ForceRestart": "false",
				"ParameterName": "max_sp_recursion_depth",
				"ParameterDescription": "The number of times that any given stored procedure may be called recursively. The default value for this option is 0, which completely disables recursion in stored procedures. The maximum value is 255."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-102400]",
				"ParameterValue": "102400",
				"ForceRestart": "false",
				"ParameterName": "max_write_lock_count",
				"ParameterDescription": "After this many write locks, allow some read locks to run in between."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-1048576]",
				"ParameterValue": "1024",
				"ForceRestart": "true",
				"ParameterName": "metadata_locks_cache_size",
				"ParameterDescription": "The size of the metadata locks cache. The server uses this cache to avoid creation and destruction of synchronization objects. This is particularly helpful on systems where such operations are expensive, such as Windows XP."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "0",
				"ForceRestart": "false",
				"ParameterName": "min_examined_row_limit",
				"ParameterDescription": "Queries that examine fewer than this number of rows are not logged to the slow query log."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1024-1048576]",
				"ParameterValue": "16384",
				"ForceRestart": "false",
				"ParameterName": "net_buffer_length",
				"ParameterDescription": "Each client thread is associated with a connection buffer and result buffer. Both begin with a size given by net_buffer_length but are dynamically enlarged up to max_allowed_packet bytes as needed. The result buffer shrinks to net_buffer_length after each SQL statement."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-1073741824]",
				"ParameterValue": "30",
				"ForceRestart": "false",
				"ParameterName": "net_read_timeout",
				"ParameterDescription": "The number of seconds to wait for more data from a connection before aborting the read."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-1073741824]",
				"ParameterValue": "10",
				"ForceRestart": "false",
				"ParameterName": "net_retry_count",
				"ParameterDescription": "If a read or write on a communication port is interrupted, retry this many times before giving up."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-1073741824]",
				"ParameterValue": "60",
				"ForceRestart": "false",
				"ParameterName": "net_write_timeout",
				"ParameterDescription": "The number of seconds to wait for a block to be written to a connection before aborting the write."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[TRUE|FALSE]",
				"ParameterValue": "FALSE",
				"ForceRestart": "false",
				"ParameterName": "old-style-user-limits",
				"ParameterDescription": "Enable old-style user limits. (Before MySQL 5.0.3, account resource limits were counted separately for each host from which a user connected rather than per account row in the user table.)"
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0|1|2]",
				"ParameterValue": "0",
				"ForceRestart": "false",
				"ParameterName": "old_passwords",
				"ParameterDescription": "This variable controls the password hashing method used by the PASSWORD() function. It also influences password hashing performed by CREATE USER and GRANT statements that specify a password using an IDENTIFIED BY clause."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[4000-1000000]",
				"ParameterValue": "655350",
				"ForceRestart": "true",
				"ParameterName": "open_files_limit",
				"ParameterDescription": "If this is not 0, then mysqld will use this value to reserve file descriptors to use with setrlimit(). If this value is 0 then mysqld will reserve max_connections*5 or max_connections + table_cache*2 (whichever is larger) number of file descriptors."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0|1]",
				"ParameterValue": "1",
				"ForceRestart": "false",
				"ParameterName": "optimizer_prune_level",
				"ParameterDescription": "Controls the heuristics applied during query optimization to prune less-promising partial plans from the optimizer search space. A value of 0 disables heuristics so that the optimizer performs an exhaustive search. A value of 1 causes the optimizer to prune plans based on the number of rows retrieved by intermediate plans."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-62]",
				"ParameterValue": "62",
				"ForceRestart": "false",
				"ParameterName": "optimizer_search_depth",
				"ParameterDescription": "The maximum depth of search performed by the query optimizer. Values larger than the number of relations in a query result in better query plans, but take longer to generate an execution plan for a query. Values smaller than the number of relations in a query return an execution plan quicker, but the resulting plan may be far from being optimal. If set to 0, the system automatically picks a reasonable value."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "1",
				"ForceRestart": "false",
				"ParameterName": "optimizer_trace_limit",
				"ParameterDescription": "The maximum number of optimizer traces to display."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "16384",
				"ForceRestart": "false",
				"ParameterName": "optimizer_trace_max_mem_size",
				"ParameterDescription": "The maximum cumulative size of stored optimizer traces."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-4294967295]",
				"ParameterValue": "-1",
				"ForceRestart": "false",
				"ParameterName": "optimizer_trace_offset",
				"ParameterDescription": "The offset of optimizer traces to display."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1024-1073741824]",
				"ParameterValue": "32768",
				"ForceRestart": "false",
				"ParameterName": "preload_buffer_size",
				"ParameterDescription": "The size of the buffer that is allocated when preloading indexes."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1024-1073741824]",
				"ParameterValue": "8192",
				"ForceRestart": "false",
				"ParameterName": "query_alloc_block_size",
				"ParameterDescription": "The allocation size of memory blocks that are allocated for objects created during statement parsing and execution."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-1073741824]",
				"ParameterValue": "1048576",
				"ForceRestart": "false",
				"ParameterName": "query_cache_limit",
				"ParameterDescription": "Do not cache results that are larger than this number of bytes."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[512-4294967295]",
				"ParameterValue": "4096",
				"ForceRestart": "false",
				"ParameterName": "query_cache_min_res_unit",
				"ParameterDescription": "The minimum size (in bytes) for blocks allocated by the query cache. The default value is 4096 (4KB)."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[100-1073741824]",
				"ParameterValue": "3145728",
				"ForceRestart": "false",
				"ParameterName": "query_cache_size",
				"ParameterDescription": "The amount of memory allocated for caching query results."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-2]",
				"ParameterValue": "0",
				"ForceRestart": "true",
				"ParameterName": "query_cache_type",
				"ParameterDescription": "Set the query cache type. Please turns on variable 'loose_innodb_primary_qcache_invalid_log' on primary node if replica's query_cache_type >= 1."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[TRUE|FALSE]",
				"ParameterValue": "FALSE",
				"ForceRestart": "false",
				"ParameterName": "query_cache_wlock_invalidate",
				"ParameterDescription": "Normally, when one client acquires a WRITE lock on a MyISAM table, other clients are not blocked from issuing statements that read from the table if the query results are present in the query cache. Setting this variable to 1 causes acquisition of a WRITE lock for a table to invalidate any queries in the query cache that refer to the table. This forces other clients that attempt to access the table to wait while the lock is in effect."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[8192-1073741824]",
				"ParameterValue": "8192",
				"ForceRestart": "false",
				"ParameterName": "query_prealloc_size",
				"ParameterDescription": "The size of the persistent buffer used for statement parsing and execution."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[4096-18446744073709551615]",
				"ParameterValue": "4096",
				"ForceRestart": "false",
				"ParameterName": "range_alloc_block_size",
				"ParameterDescription": "The size of blocks that are allocated when doing range optimization."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[TRUE|FALSE]",
				"ParameterValue": "FALSE",
				"ForceRestart": "false",
				"ParameterName": "safe-user-create",
				"ParameterDescription": "If this option is enabled, a user cannot create new MySQL users by using the GRANT statement unless the user has the INSERT privilege for the mysql.user table or any column in the table. If you want a user to have the ability to create new users that have those privileges that the user has the right to grant, you should grant the user the following privilege."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-1024]",
				"ParameterValue": "2",
				"ForceRestart": "false",
				"ParameterName": "slow_launch_time",
				"ParameterDescription": "If creating a thread takes longer than this many seconds, the server increments the Slow_launch_threads status variable."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[ON|OFF]",
				"ParameterValue": "ON",
				"ForceRestart": "false",
				"ParameterName": "slow_query_log",
				"ParameterDescription": "Specify the initial slow query log state. With no argument or an argument of 1, the --slow-query-log option enables the log. If omitted or given with an argument of 0, the option disables the log."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "(s*|REAL_AS_FLOAT|PIPES_AS_CONCAT|ANSI_QUOTES|IGNORE_SPACE|ONLY_FULL_GROUP_BY|NO_UNSIGNED_SUBTRACTION|NO_DIR_IN_CREATE|POSTGRESQL|ORACLE|MSSQL|DB2|MAXDB|NO_KEY_OPTIONS|NO_TABLE_OPTIONS|NO_FIELD_OPTIONS|MYSQL323|MYSQL40|ANSI|NO_AUTO_VALUE_ON_ZERO|NO_BACKSLASH_ESCAPES|STRICT_TRANS_TABLES|STRICT_ALL_TABLES|NO_ZERO_IN_DATE|NO_ZERO_DATE|ALLOW_INVALID_DATES|ERROR_FOR_DIVISION_BY_ZERO|TRADITIONAL|HIGH_NOT_PRECEDENCE|NO_ENGINE_SUBSTITUTION|PAD_CHAR_TO_FULL_LENGTH)(,REAL_AS_FLOAT|,PIPES_AS_CONCAT|,ANSI_QUOTES|,IGNORE_SPACE|,ONLY_FULL_GROUP_BY|,NO_UNSIGNED_SUBTRACTION|,NO_DIR_IN_CREATE|,POSTGRESQL|,ORACLE|,MSSQL|,DB2|,MAXDB|,NO_KEY_OPTIONS|,NO_TABLE_OPTIONS|,NO_FIELD_OPTIONS|,MYSQL323|,MYSQL40|,ANSI|,NO_AUTO_VALUE_ON_ZERO|,NO_BACKSLASH_ESCAPES|,STRICT_TRANS_TABLES|,STRICT_ALL_TABLES|,NO_ZERO_IN_DATE|,NO_ZERO_DATE|,ALLOW_INVALID_DATES|,ERROR_FOR_DIVISION_BY_ZERO|,TRADITIONAL|,HIGH_NOT_PRECEDENCE|,NO_ENGINE_SUBSTITUTION|,PAD_CHAR_TO_FULL_LENGTH)*",
				"ParameterValue": "''",
				"ForceRestart": "false",
				"ParameterName": "sql_mode",
				"ParameterDescription": "Modes define what SQL syntax MySQL should support and what kind of data validation checks it should perform."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[16-524288]",
				"ParameterValue": "256",
				"ForceRestart": "false",
				"ParameterName": "stored_program_cache",
				"ParameterDescription": "Sets a soft upper limit for the number of cached stored routines per connection. The value of this variable is specified in terms of the number of stored routines held in each of the two caches maintained by the MySQL Server for, respectively, stored procedures and stored functions."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[FALSE|TRUE]",
				"ParameterValue": "FALSE",
				"ForceRestart": "false",
				"ParameterName": "sysdate-is-now",
				"ParameterDescription": "SYSDATE() by default returns the time at which it executes, not the time at which the statement in which it occurs begins executing. This differs from the behavior of NOW(). This option causes SYSDATE() to be an alias for NOW(). For information about the implications for binary logging and replication."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[400-80480]",
				"ParameterValue": "16384",
				"ForceRestart": "false",
				"ParameterName": "table_definition_cache",
				"ParameterDescription": "The number of table definitions (from .frm files) that can be stored in the definition cache. If you use a large number of tables, you can create a large table definition cache to speed up opening of tables. The table definition cache takes less space and does not use file descriptors, unlike the normal table cache. The minimum and default values are both 400."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-524288]",
				"ParameterValue": "16384",
				"ForceRestart": "false",
				"ParameterName": "table_open_cache",
				"ParameterDescription": "The number of open tables for all threads. Increasing this value increases the number of file descriptors that mysqld requires. You can check whether you need to increase the table cache by checking the Opened_tables status variable. If the value of Opened_tables is large and you do not use FLUSH TABLES often (which just forces all tables to be closed and reopened), then you should increase the value of the table_open_cache variable."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1-64]",
				"ParameterValue": "32",
				"ForceRestart": "true",
				"ParameterName": "table_open_cache_instances",
				"ParameterDescription": "The number of open tables cache instances."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[FALSE|TRUE]",
				"ParameterValue": "TRUE",
				"ForceRestart": "true",
				"ParameterName": "temp-pool",
				"ParameterDescription": "This option is ignored except on Linux. On Linux, it causes most temporary files created by the server to use a small set of names, rather than a unique name for each new file. This works around a problem in the Linux kernel dealing with creating many new files with different names. With the old behavior, Linux seems to “leak” memory, because it is being allocated to the directory entry cache rather than to the disk cache."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[0-16384]",
				"ParameterValue": "256",
				"ForceRestart": "false",
				"ParameterName": "thread_cache_size",
				"ParameterDescription": "How many threads the server should cache for reuse. When a client disconnects, the client's threads are put in the cache if there are fewer than thread_cache_size threads there. Requests for threads are satisfied by reusing threads taken from the cache if possible, and only when the cache is empty is a new thread created. This variable can be increased to improve performance if you have a lot of new connections. Normally, this does not provide a notable performance improvement if you have a good thread implementation. However, if your server sees hundreds of connections per second you should normally set thread_cache_size high enough so that most new connections use cached threads. By examining the difference between the Connections and Threads_created status variables, you can see how efficient the thread cache is."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[131072-1073741824]",
				"ParameterValue": "262144",
				"ForceRestart": "true",
				"ParameterName": "thread_stack",
				"ParameterDescription": "The stack size of each thread."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[262144-10737418240]",
				"ParameterValue": "2097152",
				"ForceRestart": "false",
				"ParameterName": "tmp_table_size",
				"ParameterDescription": "The maximum size of internal in-memory temporary tables."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[READ-UNCOMMITTED|READ-COMMITTED|REPEATABLE-READ]",
				"ParameterValue": "READ-COMMITTED",
				"ForceRestart": "true",
				"ParameterName": "transaction-isolation",
				"ParameterDescription": "Sets the default transaction isolation level."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1024-4294967295]",
				"ParameterValue": "8192",
				"ForceRestart": "false",
				"ParameterName": "transaction_alloc_block_size",
				"ParameterDescription": "The amount in bytes by which to increase a per-transaction memory pool which needs memory. See the description of transaction_prealloc_size."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[1024-4294967295]",
				"ParameterValue": "4096",
				"ForceRestart": "false",
				"ParameterName": "transaction_prealloc_size",
				"ParameterDescription": "There is a per-transaction memory pool from which various transaction-related allocations take memory. The initial size of the pool in bytes is transaction_prealloc_size. For every allocation that cannot be satisfied from the pool because it has insufficient memory available, the pool is increased by transaction_alloc_block_size bytes. When the transaction ends, the pool is truncated to transaction_prealloc_size bytes."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[YES|NO]",
				"ParameterValue": "YES",
				"ForceRestart": "false",
				"ParameterName": "updatable_views_with_limit",
				"ParameterDescription": "This variable controls whether updates to a view can be made when the view does not contain all columns of the primary key defined in the underlying table, if the update statement contains a LIMIT clause. (Such updates often are generated by GUI tools.) An update is an UPDATE or DELETE statement. Primary key here means a PRIMARY KEY, or a UNIQUE index in which no column can contain NULL."
			},
			{
				"ForceModify": "true",
				"CheckingCode": "[60-259200]",
				"ParameterValue": "86400",
				"ForceRestart": "false",
				"ParameterName": "wait_timeout",
				"ParameterDescription": "The number of seconds the server waits for activity on a noninteractive connection before closing it."
			}
		]
	},
	"RequestId": "D963934D-8605-4473-8EAC-54C719******",
	"Engine": "POLARDB"
}

错误码

访问错误中心查看更多错误码。