Bug #85682 | [Warning] option 'thread_cache_size': value -1 adjusted to 0 | ||
---|---|---|---|
Submitted: | 29 Mar 2017 11:54 | Modified: | 30 Mar 2017 7:24 |
Reporter: | kfpanda kf | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Options | Severity: | S3 (Non-critical) |
Version: | 5.7.17 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[29 Mar 2017 11:54]
kfpanda kf
[30 Mar 2017 7:24]
MySQL Verification Team
Hello kfpanda kf, Thank you for the report. Imho autosizing here means that the user does not have to do it. Per manual "The default value is based on the following formula, capped to a limit of 100: 8 + (max_connections / 100) Also, allowed default value is between 0 and 16384 In my environment: root@localhost [(none)]> set global thread_cache_size = DEFAULT; Query OK, 0 rows affected (0.00 sec) root@localhost [(none)]> show variables like 'thread_cache_size'; +-------------------+-------+ | Variable_name | Value | +-------------------+-------+ | thread_cache_size | 9 | +-------------------+-------+ 1 row in set (0.01 sec) root@localhost [(none)]> show global variables like 'max_connections'; +-----------------+-------+ | Variable_name | Value | +-----------------+-------+ | max_connections | 151 | +-----------------+-------+ 1 row in set (0.00 sec) root@localhost [(none)]> select 8+(151/100); +-------------+ | 8+(151/100) | +-------------+ | 9.5100 | +-------------+ 1 row in set (0.00 sec) Thanks, Umesh