Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
10.11.2
-
Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-70-generic x86_64)
Description
It started happening soon after upgrade to 10.11.2 version from 10.10 I believe. The problem starts when PHP scripts starts using 250-350 threads for INSERT statements mostly (SELECT statements are frequent too). On average MariaDB receives around 6000 queries per second, but problem comes even when it is just 2000 queries per second.
There is 1 master and 4 replicas (each using 16 parallel slave threads for replication).
At some point server (sometimes one sometimes two) - either master or replica stop processing any INSERT or SELECT statements. Process list then shows several hundred threads connected and they show time in many minutes or hours. Stopping any further queries to that affected server does not resolve anything - nothing changes for hours.
When this happens - a simple CONNECT to MariaDB is measured and it usually shows connection time of 60-460 ms instead of normal 0.5-1.1ms.
When I try to kill all threads one by one - they are killed, process list shows them as killed but present on the list.
If then (or before) I try to use systemctl stop mariadb - server is not stopped for hours (same with restart). The only option is to find any mariadb process and issue KILL -9 and then start Mariadb again which then starts in recovery mode. All tables are InnoDB in the database.
Servers, which do not receive many SELECT statements (the last 2 on the image list) - they never get such a problem thus I believe replication is not an issue. Replicas are READ ONLY.
This happens about once or twice a day at different times but when number of queries is on a high side. There is no shortage of RAM or disk.
Attachments
Issue Links
- duplicates
-
MDEV-29835 Partial server freeze
- Closed
- relates to
-
MDEV-33185 Connection timeout/slowdown upon increased load
- Open