Bug #89503 | innodb_purge_stop_now=1 causes purge_sys->n_stop == 0 on shutdown | ||
---|---|---|---|
Submitted: | 1 Feb 2018 23:46 | Modified: | 25 Feb 2018 21:20 |
Reporter: | Roel Van de Paar | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S6 (Debug Builds) |
Version: | 8.0.4rc, 5.7.21 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[1 Feb 2018 23:46]
Roel Van de Paar
[2 Feb 2018 6:50]
MySQL Verification Team
Hello Roel, Thank you for the report and feedback. Observed that debug build is affected. Thanks, Umesh
[2 Feb 2018 6:56]
MySQL Verification Team
-- This is even observed with 5.7.21 debug build (gdb) bt #0 0x00007f658d515771 in pthread_kill () from /lib64/libpthread.so.0 #1 0x000000000185f6ad in my_write_core (sig=6) at /export/home/pb2/build/sb_0-25673884-1510161542.84/mysqlcom-pro-5.7.21/mysys/stacktrace.c:249 #2 0x0000000000ea9966 in handle_fatal_signal (sig=6) at /export/home/pb2/build/sb_0-25673884-1510161542.84/mysqlcom-pro-5.7.21/sql/signal_handler.cc:220 #3 <signal handler called> #4 0x00007f658bf0f5d7 in raise () from /lib64/libc.so.6 #5 0x00007f658bf10cc8 in abort () from /lib64/libc.so.6 #6 0x0000000001addd64 in ut_dbg_assertion_failed (expr=0x2313b7b "purge_sys->n_stop == 0", file=0x2312ef0 "/export/home/pb2/build/sb_0-25673884-1510161542.84/mysqlcom-pro-5.7.21/storage/innobase/srv/srv0srv.cc", line=2709) at /export/home/pb2/build/sb_0-25673884-1510161542.84/mysqlcom-pro-5.7.21/storage/innobase/ut/ut0dbg.cc:67 #7 0x0000000001a74ce0 in srv_purge_coordinator_suspend (slot=0x4a03290, rseg_history_len=0) at /export/home/pb2/build/sb_0-25673884-1510161542.84/mysqlcom-pro-5.7.21/storage/innobase/srv/srv0srv.cc:2709 #8 0x0000000001a75047 in srv_purge_coordinator_thread (arg=0x0) at /export/home/pb2/build/sb_0-25673884-1510161542.84/mysqlcom-pro-5.7.21/storage/innobase/srv/srv0srv.cc:2792 #9 0x00007f658d510df5 in start_thread () from /lib64/libpthread.so.0 #10 0x00007f658bfd060d in clone () from /lib64/libc.so.6 (gdb)
[25 Feb 2018 21:20]
Roel Van de Paar
Any updates?