[TiDB Usage Environment] Production Environment
[TiDB Version] v6.1.7
[Reproduction Path] Use the command tiup cluster edit-config xxx to add the table_open_cache_instances configuration. The default value of this parameter is 1, and it is hoped to adjust it to 16.
[Encountered Problem: Problem Phenomenon and Impact] After executing the command tiup cluster reload xx, the following error is reported: contained invalid configuration options: table_open_cache_instances. Is it possible that this parameter does not support modification?
These parameters in the TiDB source code comments exist for MySQL compatibility, and changing them is meaningless.
// The following sysVars are noops.
// Some applications will depend on certain variables to be present or settable,
// for example query_cache_time. These are included for MySQL compatibility,
// but changing them has no effect on behavior.
To modify the output, you need to execute the set statement. It cannot be changed in the configuration file. Note the difference between system variables and configuration parameters.
This parameter is only effective for MySQL. TiDB includes this parameter by default for compatibility with MySQL, but it does not have any actual effect.
For TiDB’s cache, you need to refer to TiDB’s system for configuration:
Reference for debugging and configuration process cases: