Details
-
Bug
-
Status: Needs Feedback (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.11.7
-
None
-
CentOS Stream release 8
4.18.0-448.el8.x86_64
x86_64 GNU/Linux
Description
Hello
I've got bug with corruption of system table mysql.gtid_slave_pos
It happened with one of the many (the same) replicas
The replica got error and gone to segfault
2024-11-09 20:29:36 0x7eb5e41a0700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.11.7/storage/innobase/buf/buf0lru.cc line 281 |
InnoDB: Failing assertion: !block->page.in_file()
|
..
|
241109 20:32:27 [ERROR] mysqld got signal 6 ;
|
Sorry, we probably made a mistake, and this is a bug
|
But restart of instance causes corruption of table mysql.gtid_slave_pos and replication is stopped .
You can find details in attached mysql.log
Unfortunately the coredump was not created on disk
I have only coredumctl information
PID: 3453355 (mariadbd)
|
UID: 993 (mysql)
|
GID: 990 (mysql)
|
Signal: 6 (ABRT)
|
Timestamp: Sat 2024-11-09 20:30:37 UTC (1 day 17h ago)
|
Command Line: /usr/sbin/mariadbd |
Executable: /usr/sbin/mariadbd |
Control Group: /
|
Slice: -.slice
|
Boot ID: c6f5a3dc2df2468c83467be5777c3c23
|
Machine ID: c298002eb4c44bcabbeaa778ed312228
|
Hostname: sc-db-105-ams17-ah0848
|
Storage: none
|
Message: Process 3453355 (mariadbd) of user 993 dumped core.
|