Multiple issues with extra_max_connections
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.1 |
Invalid
|
Undecided
|
Unassigned | |||
5.5 |
Triaged
|
Medium
|
Unassigned | |||
5.6 |
Triaged
|
Medium
|
Unassigned | |||
5.7 |
Triaged
|
Medium
|
Unassigned |
Bug Description
extra_max_
"
If extra-port is <> 0 then you can connect max_connections number of normal threads + 1 extra SUPER user through the 'extra-port' TCP/IP port
"
I guess it meant to say "... you can connect extra_max_
However, unless I'm missing something, extra_max_
1. create_new_thread() checks against thd->scheduler-
2. but sql_authenticate() checks the global max_connections value (i.e. the value of max-connections rather than extra-max-
Another related issue is that fix_max_ connections( ) (called when extra_max_ connections is updated dynamically) would use the global max_connections value in the call to resize_thr_alarm().