Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.5.20, 10.6.13, 10.6.15
-
K8s, amd64, occurs both in official mariadb:10.6.15 and quay.io/mariadb-foundation/mariadb-debug:10.6
Description
Hi,
week ago our production database cluster (1 master, 4 replicas, maxscale as proxy) started to deadlock master approx. every 12 hours. We are still looking for trigger but without any success. No obvious problematic query in PROCESSLIST, nothing ![]()
Finally today we were able to get decent coredump, using quay.io/mariadb-foundation/mariadb-debug:10.6 image. Exact version is 10.6.16-MariaDB-1:10.6.16+maria~ubu2004-log source revision: 07494006dd0887ebfb31564a8fd4c59cf1b299e9, exact image version docker.io/library/mariadb@sha256:fcbe381e5fef20c7a2932b52a070f58987b770c651aedf705332e54d1dfd465f
SELECTs seems to be running OK, DML queries are blocked. Some in "opening table" some in "sending data".
I'm attaching both server log, full backtrace and I also have coredump, but it is 700MB bzipped so not attaching but is available.
Attachments
Issue Links
- is caused by
-
MDEV-30753 Possible corruption due to trx_purge_free_segment()
-
- Closed
-