Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0.15, 10.1.10, 10.2.0, 10.3.0, 10.4.0, 10.5.0
Description
SET GLOBAL innodb_adaptive_flushing_lwm=0.0;
|
CREATE TABLE t (c DOUBLE) ENGINE=InnoDB;
|
SET GLOBAL innodb_io_capacity=18446744073709551615;
|
SELECT SLEEP (3);
|
Leads to:
10.6.0 9118fd360a3da0bba521caf2a35c424968235ac4 (Debug) |
mysqld: /test/10.6_dbg/storage/innobase/buf/buf0flu.cc:1890: ulint af_get_pct_for_lsn(lsn_t): Assertion `srv_max_io_capacity >= srv_io_capacity' failed.
|
10.6.0 9118fd360a3da0bba521caf2a35c424968235ac4 (Debug) |
Core was generated by `/test/MD010121-mariadb-10.6.0-linux-x86_64-dbg/bin/mysqld --no-defaults --core-'.
|
Program terminated with signal SIGABRT, Aborted.
|
#0 __pthread_kill (threadid=<optimized out>, signo=signo@entry=6)
|
at ../sysdeps/unix/sysv/linux/pthread_kill.c:56
|
[Current thread is 1 (Thread 0x14f13c652700 (LWP 1553990))]
|
(gdb) bt
|
#0 __pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ../sysdeps/unix/sysv/linux/pthread_kill.c:56
|
#1 0x000055ee02c440d7 in my_write_core (sig=sig@entry=6) at /test/10.6_dbg/mysys/stacktrace.c:424
|
#2 0x000055ee023d8ab1 in handle_fatal_signal (sig=6) at /test/10.6_dbg/sql/signal_handler.cc:330
|
#3 <signal handler called>
|
#4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
|
#5 0x000014f145c21859 in __GI_abort () at abort.c:79
|
#6 0x000014f145c21729 in __assert_fail_base (fmt=0x14f145db7588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55ee03064238 "srv_max_io_capacity >= srv_io_capacity", file=0x55ee03063238 "/test/10.6_dbg/storage/innobase/buf/buf0flu.cc", line=1890, function=<optimized out>) at assert.c:92
|
#7 0x000014f145c32f36 in __GI___assert_fail (assertion=assertion@entry=0x55ee03064238 "srv_max_io_capacity >= srv_io_capacity", file=file@entry=0x55ee03063238 "/test/10.6_dbg/storage/innobase/buf/buf0flu.cc", line=line@entry=1890, function=function@entry=0x55ee03064260 "ulint af_get_pct_for_lsn(lsn_t)") at assert.c:101
|
#8 0x000055ee02ac2529 in af_get_pct_for_lsn (age=1616) at /test/10.6_dbg/storage/innobase/buf/buf0flu.cc:1890
|
#9 page_cleaner_flush_pages_recommendation (dirty_pct=0.21037000371241182, dirty_blocks=17, oldest_lsn=43230, last_pages_in=0) at /test/10.6_dbg/storage/innobase/buf/buf0flu.cc:1921
|
#10 buf_flush_page_cleaner () at /test/10.6_dbg/storage/innobase/buf/buf0flu.cc:2170
|
#11 0x000014f14612f609 in start_thread (arg=<optimized out>) at pthread_create.c:477
|
#12 0x000014f145d1e293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
|
Bug confirmed present in:
MariaDB: 10.5.9 (dbg), 10.6.0 (dbg)
Bug (or feature/syntax) confirmed not present in:
MariaDB: 10.2.37 (dbg), 10.2.37 (opt), 10.3.28 (dbg), 10.3.28 (opt), 10.4.18 (dbg), 10.4.18 (opt), 10.5.9 (opt), 10.6.0 (opt)
MySQL: 5.5.62 (dbg), 5.5.62 (opt), 5.6.50 (dbg), 5.6.50 (opt), 5.7.32 (dbg), 5.7.32 (opt), 8.0.22 (dbg), 8.0.22 (opt)
10.4 Does not crash at all on the same.
There is also this:
10.4.18 3454b5cf35a61e8f6cfab376638520dee4a50609 (Debug) |
10.4.18>SET GLOBAL innodb_io_capacity=18446744073709551615;
|
Query OK, 0 rows affected, 2 warnings (0.000 sec)
|
|
10.4.18>SHOW WARNINGS;
|
+---------+------+------------------------------------------------------------------------------------------------------------+
|
| Level | Code | Message |
|
+---------+------+------------------------------------------------------------------------------------------------------------+
|
| Warning | 1210 | Setting innodb_io_capacity to 18446744073709551615 higher than innodb_io_capacity_max 18446744073709551614 |
|
| Warning | 1210 | Setting innodb_max_io_capacity to 18446744073709551614 |
|
+---------+------+------------------------------------------------------------------------------------------------------------+
|
2 rows in set (0.000 sec)
|
|
10.4.18>SELECT @@GLOBAL.innodb_max_io_capacity;
|
ERROR 1193 (HY000): Unknown system variable 'innodb_max_io_capacity'
|
10.4.18>SELECT @@GLOBAL.innodb_io_capacity;
|
+-----------------------------+
|
| @@GLOBAL.innodb_io_capacity |
|
+-----------------------------+
|
| 18446744073709551615 |
|
+-----------------------------+
|
1 row in set (0.000 sec)
|
Not sure if that is a separate off-by-one bug and/or a minor functionality bug or not.
Also see MDEV-7035.
Attachments
Issue Links
- is caused by
-
MDEV-7035 Remove innodb_io_capacity setting depending on setting of innodb_io_capacity_max
- Closed