Details
Description
The test innodb.undo_truncate, which in MDEV-26672 was updated to issue a slow shutdown, is causing assertion failures in 10.3 and 10.4. 10.5 and later are unaffected, likely thanks to MDEV-16264 removing thd_destructor_proxy.
10.2 is likely affected as well, but the test innodb.undo_truncate is not issuing a slow shutdown (innodb_fast_shutdown=0) there. Here is a sample failure:
10.3 333d6c30f87a7862a2d6ca379c49e2ea46451ebc |
innodb.undo_truncate '2,32k,innodb' w3 [ fail ] Found warnings/errors in server log file!
|
Test ended at 2021-09-29 17:16:03
|
line
|
mysqld: /home/buildbot/buildbot/build/mariadb-10.3.32/sql/sql_list.h:642: void ilink::assert_linked(): Assertion `prev != 0 && next != 0' failed.
|
Attempting backtrace. You can use the following information to find out
|
mysqld: /home/buildbot/buildbot/build/mariadb-10.3.32/sql/sql_list.h:642: void ilink::assert_linked(): Assertion `prev != 0 && next != 0' failed.
|
^ Found warnings in /mnt/buildbot/build/mariadb-10.3.32/mysql-test/var/3/log/mysqld.1.err
|
…
|
#4 0xb703dd8b in __assert_fail () from /lib/i386-linux-gnu/libc.so.6
|
#5 0x803fb73f in ilink::assert_linked (this=0xb23021a0) at /home/buildbot/buildbot/build/mariadb-10.3.32/sql/sql_list.h:642
|
#6 0x803fcd37 in unlink_not_visible_thd (thd=0xb23021a0) at /home/buildbot/buildbot/build/mariadb-10.3.32/sql/sql_class.h:4906
|
#7 0x804b8357 in destroy_thd (thd=0xb23021a0) at /home/buildbot/buildbot/build/mariadb-10.3.32/sql/sql_class.cc:4792
|
#8 0x80b635ab in thd_destructor_proxy () at /home/buildbot/buildbot/build/mariadb-10.3.32/storage/innobase/handler/ha_innodb.cc:343
|
Attachments
Issue Links
- is duplicated by
-
MDEV-13644 encryption.innochecksum, innodb.innodb-page_compression_default, failed in bb with Assertion `prev != 0 && next != 0' failed
- Closed
- relates to
-
MDEV-26672 innodb_undo_log_truncate may cause the transaction ID sequence to be reset
- Closed