Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5.37-galera
-
None
Description
my.cnf:
max_connections=200
|
wsrep_slave_threads=400
|
# /etc/init.d/mysql restart ; mysql -u openquery
|
* Stopping MariaDB database server mysqld [ OK ]
|
* Starting MariaDB database server mysqld [ OK ]
|
* Checking for corrupt, not cleanly closed and upgrade needing tables.
|
ERROR 1040 (HY000): Too many connections
|
# ERROR 1040 (HY000): Too many connections
|
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
my.cnf: max_connections=200 wsrep_slave_threads=400 # /etc/init.d/mysql restart ; mysql -u openquery * Stopping MariaDB database server mysqld [ OK ] * Starting MariaDB database server mysqld [ OK ] * Checking for corrupt, not cleanly closed and upgrade needing tables. ERROR 1040 (HY000): Too many connections # ERROR 1040 (HY000): Too many connections |
my.cnf: {noformat} max_connections=200 wsrep_slave_threads=400 {noformat} {noformat} # /etc/init.d/mysql restart ; mysql -u openquery * Stopping MariaDB database server mysqld [ OK ] * Starting MariaDB database server mysqld [ OK ] * Checking for corrupt, not cleanly closed and upgrade needing tables. ERROR 1040 (HY000): Too many connections # ERROR 1040 (HY000): Too many connections {noformat} |
| Assignee | Nirbhay Choubey [ nirbhay_c ] | |
| Labels | galera |
My basis for the bug report is the max_connections definition:
https://mariadb.com/kb/en/server-system-variables/#max_connections
max_connections Description: The maximum number of simultaneous client connections
Though a wsrep_slave_threads shows up in the process list its not actually a client connection.
I see the wsrep_slave_threads also affects the status threads_connected.
| Variable_name | Value |
| Threads_connected | 66 |
I appreciate that even async replication took two "connections" as a slave and 1 per slave as a master however it seems wsrep_slave_threads can make much more of an impact into the max_connections.
I'm in favour of preserving the definition of max_connections as client connections but alter the statusThreads_connected definition to include systems threads.
| Status | Open [ 1 ] | In Progress [ 3 ] |
Hi Daniel,
I too think "system" threads should not be included under "connection" threads. However,
I do not feel like changing the definition of Threads_connected, would rather introduce a
new status variable representing wsrep thread count. Thanks!
> I too think "system" threads should not be included under "connection" threads.
Thank you. I hoped you see it that way too.
> However,I do not feel like changing the definition of Threads_connected, would rather introduce a
new status variable representing wsrep thread count.
works for me. 
| Fix Version/s | 5.5.38-galera [ 15901 ] |
| Fix Version/s | 10.0.11-galera [ 15900 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Workflow | defaullt [ 39931 ] | MariaDB v2 [ 43822 ] |
| Workflow | MariaDB v2 [ 43822 ] | MariaDB v3 [ 63018 ] |
| Workflow | MariaDB v3 [ 63018 ] | MariaDB v4 [ 147866 ] |
I'm not sure it's actually wrong, assigning to nirbhay_c to decide.