Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
10.6.12
-
Centos7 (Reproductible on Rocky8)
MariaDB-client.x86_64 10.6.12-1.el7.centos @mariadb
MariaDB-common.x86_64 10.6.12-1.el7.centos @mariadb
MariaDB-compat.x86_64 10.6.12-1.el7.centos @mariadb
MariaDB-devel.x86_64 10.6.12-1.el7.centos @mariadb
MariaDB-server.x86_64 10.6.12-1.el7.centos @mariadb
MariaDB-shared.x86_64 10.6.12-1.el7.centos @mariadb
MariaDB-test.x86_64 10.6.12-1.el7.centos @mariadb
galera-4.x86_64 26.4.14-1.el7.centos @mariadb
CentOS Linux release 7.9.2009 (Core)
Memory: 192 GB in test / 256 GB in ProdCentos7 (Reproductible on Rocky8) MariaDB-client.x86_64 10.6.12-1.el7.centos @mariadb MariaDB-common.x86_64 10.6.12-1.el7.centos @mariadb MariaDB-compat.x86_64 10.6.12-1.el7.centos @mariadb MariaDB-devel.x86_64 10.6.12-1.el7.centos @mariadb MariaDB-server.x86_64 10.6.12-1.el7.centos @mariadb MariaDB-shared.x86_64 10.6.12-1.el7.centos @mariadb MariaDB-test.x86_64 10.6.12-1.el7.centos @mariadb galera-4.x86_64 26.4.14-1.el7.centos @mariadb CentOS Linux release 7.9.2009 (Core) Memory: 192 GB in test / 256 GB in Prod
Description
After upgrade from 10.3 to 10.6.12, queries stay running forever. if I kill the query, it stays in status "Killed" forever.
Only way is to kill the mysql process.
Maybe related to MDEV-30638 or MDEV-29835 but I'm not sure
I generated a core dump (17 GB) and output of SHOW ENGINE INNODB STATUS
Let me know how I can send you the core dump. It's really critical for us, affecting Production
Attachments
Issue Links
- duplicates
-
MDEV-29835 Partial server freeze
- Closed