Setting innodb_log_archive crashes --innodb-read-only server | InnoDB: Failing assertion: !srv_read_only_mode in log0log.cc line 2192
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Medium
|
Laurynas Biveinis | ||
5.1 |
Invalid
|
Undecided
|
Unassigned | ||
5.5 |
Invalid
|
Undecided
|
Unassigned | ||
5.6 |
Fix Released
|
Medium
|
Laurynas Biveinis |
Bug Description
** Testcase
When we start mysql server with --innodb-
DROP DATABASE test;CREATE DATABASE test;USE test;
SET GLOBAL innodb_
SET GLOBAL innodb_
The attached tarball (1439446057.tar.gz) gives the testcase as an exact match of our system, including some handy utilities
$ vi 1439446057_mybase # STEP1: Update the base path in this file (usually the only change required!). If you use a non-binary distribution, please update SOURCE_DIR location also
$ ./1439446057_init # STEP2: Initializes the data dir
$ ./1439446057_start # STEP3: Starts mysqld
$ ./1439446057_cl # STEP4: To check mysqld is up
$ ./1439446057_
$ ./1439446057_run # OPTIONAL: Run the testcase with the mysql CLI (may not reproduce the issue, as the pquery binary was used for the original testcase reduction)
$ vi /dev/shm/
$ ./1439446057_gdb # OPTIONAL: Brings you to a gdb prompt with gdb attached to the used mysqld and attached to the generated core
$ ./1439446057_
** GDB info
+bt
#0 0x00007f76f2081771 in __pthread_kill (threadid=
#1 0x0000000000abfcc4 in my_write_core (sig=6) at /mnt/workspace/
#2 0x00000000007330dd in handle_fatal_signal (sig=6) at /mnt/workspace/
#3 <signal handler called>
#4 0x00007f76f0c855d7 in __GI_raise (sig=sig@entry=6) at ../nptl/
#5 0x00007f76f0c86cc8 in __GI_abort () at abort.c:90
#6 0x0000000000b48a99 in log_checkpoint (sync=1, write_always=1) at /mnt/workspace/
#7 0x0000000000b4ae4a in log_archive_stop () at /mnt/workspace/
#8 0x0000000000b4afe7 in log_archive_
#9 0x0000000000aed61d in innodb_
#10 0x00000000007ff35e in sys_var_
#11 0x0000000000730afd in sys_var::update (this=0x7f76ebf
#12 0x0000000000731c98 in set_var::update (this=0x7f76da8
#13 0x000000000073180c in sql_set_variables (thd=0x7f76ebfe
#14 0x00000000007e9f51 in mysql_execute_
#15 0x00000000007f14ea in mysql_parse (thd=0x7f76ebfe
#16 0x00000000007e329e in dispatch_command (command=COM_QUERY, thd=0x7f76ebfe7000, packet=
#17 0x00000000007e210c in do_command (thd=0x7f76ebfe
#18 0x00000000007a9f60 in do_handle_
#19 0x00000000007a99e0 in handle_
#20 0x0000000000dd14df in pfs_spawn_thread (arg=0x7f76eeff
#21 0x00007f76f207cdf5 in start_thread (arg=0x7f76f264
#22 0x00007f76f0d461ad in clone () at ../sysdeps/
(gdb) +set logging off
summary: |
- InnoDB: Failing assertion: !srv_read_only_mode in log0log.cc line 2192 + Setting innodb_log_archive crashes --innodb-read-only server | InnoDB: + Failing assertion: !srv_read_only_mode in log0log.cc line 2192 |
tags: | added: low-hanging-fruit xtradb |
The server crashes the same if --innodb-read-only is set, which is a more general bug case.