[Maria-discuss] connection limit, connection drops
Hello, I'm using MariaDB 5.5.33a on Debian Wheezy. I have problems with connections from our PHP Application to MariaDB. Then there is high traffic the concurrent connections goes up to 1700 - 2200. If we have 1700 - 2200 concurrent connections we have sporadic connection drops like: "Can't connect to mysql ....." I have bumped the max_connection to 10000 and set some sysctl variables: echo 55536 > cat /proc/sys/net/core/somaxconn echo 10000 > /proc/sys/net/core/netdev_max_backlog echo "1024 65535" > /proc/sys/net/ipv4/ip_local_port_range echo "15"> /proc/sys/net/ipv4/tcp_fin_timeout I have also bumped up the open files for the MySQL user. The Mysql user of our application has no user connection limit in mysql.user. The error is still present, does anybody has a idea about it? Thanks! Jonas
Am 16.09.2014 um 10:32 schrieb Jonas Genannt:
I'm using MariaDB 5.5.33a on Debian Wheezy.
I have problems with connections from our PHP Application to MariaDB. Then there is high traffic the concurrent connections goes up to 1700 - 2200.
If we have 1700 - 2200 concurrent connections we have sporadic connection drops like: "Can't connect to mysql ....."
I have bumped the max_connection to 10000 and set some sysctl variables:
echo 55536 > cat /proc/sys/net/core/somaxconn echo 10000 > /proc/sys/net/core/netdev_max_backlog echo "1024 65535" > /proc/sys/net/ipv4/ip_local_port_range echo "15"> /proc/sys/net/ipv4/tcp_fin_timeout
I have also bumped up the open files for the MySQL user.
The Mysql user of our application has no user connection limit in mysql.user.
The error is still present, does anybody has a idea about it?
* setup one ore more replication slaves * spread read-only queries over the slaves depending on what that many connections are doing with the database that may improve performance in general dramatically http://php.net/manual/de/book.mysqlnd-ms.php may help to spread select queries without touching the app itself
Hello,
The error is still present, does anybody has a idea about it?
* setup one ore more replication slaves * spread read-only queries over the slaves
depending on what that many connections are doing with the database that may improve performance in general dramatically
yes I know that. We have a running slave but only for HA (failover). I have problems to expand the app to query the slave. I believed that MariaDB can handle more concurrent mysql connection at a time. Greets, Jonas
Am 16.09.2014 um 11:22 schrieb Jonas Genannt:
The error is still present, does anybody has a idea about it?
* setup one ore more replication slaves * spread read-only queries over the slaves
depending on what that many connections are doing with the database that may improve performance in general dramatically
yes I know that. We have a running slave but only for HA (failover).
I have problems to expand the app to query the slave. I believed that MariaDB can handle more concurrent mysql connection at a time
you should not stop reading premature, otherwise you have seen a possible solution without touching the app
participants (2)
-
Jonas Genannt -
Reindl Harald