Details
-
Bug
-
Status: Open (View Workflow)
-
Critical
-
Resolution: Unresolved
-
11.6.2
-
None
-
None
-
None
-
PROD
Description
We upgraded our MariaDB from 10.4.18 to 11.6.2, crashing when it is running the show global status command [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
db1491.lon5
Aug 03 01:14:21 db1491.lon5.omniture.com systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
db1497.lon5
Aug 03 01:13:52 db1497.lon5.omniture.com systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
db1498.lon5
Aug 03 01:13:55 db1498.lon5.omniture.com systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
db3480.or1
Aug 03 01:11:30 db3480.or1.omniture.com systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
db714.or1
Aug 03 01:17:03 db714.or1.omniture.com systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
db911.lon5
Aug 03 01:17:31 db911.lon5.omniture.com systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
db4042.sin2
Aug 03 01:12:59 db4042.sin2.omniture.com systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
db1491.lon5
2025-08-03 1:14:19 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
db1497.lon5
2025-08-03 1:13:51 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
db1498.lon5
2025-08-03 1:13:54 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
db714.or1
2025-08-03 1:16:50 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
db911.lon5
2025-08-03 1:17:30 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
db4042.sin2
2025-08-03 1:12:57 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
[rmekala@db85300.or1 ~]$ for i in `cat d5`; do echo $i; ssh $i "sudo zcat /raid/logs/process-list.2.gz|tail -1"; done
db1491.lon5
2025-08-03 01:13:03 10862893 admin_scripts 127.0.0.1:36270 test Query 526 Filling schema table SHOW GLOBAL STATUS
db1497.lon5
db1498.lon5
2025-08-03 01:13:05 3332817 admin_scripts 127.0.0.1:49016 test Query 552 Filling schema table SHOW GLOBAL STATUS
db3480.or1
2025-08-03 01:11:04 20603313 admin_scripts 127.0.0.1:53074 test Query 564 Filling schema table SHOW GLOBAL STATUS
db714.or1
2025-08-03 01:15:04 9324880 admin_scripts 127.0.0.1:33104 test Query 505 Filling schema table SHOW GLOBAL STATUS
db911.lon5
2025-08-03 01:17:06 22399352 admin_scripts 127.0.0.1:33702 test Query 587 Filling schema table SHOW GLOBAL STATUS
db4042.sin2
2025-08-03 01:11:06 8990467 admin_scripts 127.0.0.1:36848 test Query 491 Filling schema table SHOW GLOBAL STATUS
Attachments
Issue Links
- relates to
-
MDEV-35424 False alarm/crash: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch
-
- Needs Feedback
-
-
MDEV-37352 InnoDB: InnoDB: Long wait (… seconds) for double-write buffer flush
-
- Open
-