Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6
-
None
Description
Start server with --innodb_thread_concurrency=0 --innodb_log_file_size=1M --innodb_log_files_in_group=1
(innodb_thread_concurrency=0 is actually default, so it can be omitted).
2017-11-21 23:45:22 140609571486592 [ERROR] InnoDB: Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency=0. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html
|
2017-11-21 23:45:22 140609571486592 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[2120] with error Generic error
|
Attachments
Issue Links
- is blocked by
-
MDEV-14425 Change the InnoDB redo log format to reduce write amplification
-
- Closed
-
-
MDEV-21174 Refactor mlog_write_ulint, mlog_memset, mlog_write_string
-
- Closed
-
- relates to
-
MDEV-23379 Deprecate and ignore options for InnoDB concurrency throttling
-
- Closed
-
-
MDEV-23382 Change DB_ROLL_PTR format to allow more than 128 concurrent START TRANSACTION
-
- Open
-
-
MDEV-23855 InnoDB log checkpointing causes regression for write-heavy OLTP
-
- Closed
-
-
MDEV-27268 Failed InnoDB initialization leaves garbage files behind
-
- Closed
-
-
MDEV-27774 Reduce scalability bottlenecks in mtr_t::commit()
-
- Closed
-
-
MDEV-27803 MariaDB binlog corruption when "No space left on device" and stuck session killed by client
-
- Open
-
-
MDEV-21923 Write redo log concurrently without lock
-
- Needs Feedback
-
-
MDEV-22325 ib_logfile0 is too small for innodb_thread_concurrency=0. The size of ib_logfile0 should be bigger than 200 kB * innodb_thread_concurrency.
-
- Closed
-
-
MDEV-25611 RESET MASTER still causes the server to hang
-
- Closed
-
-
MDEV-27784 log_overwrite_warning displays an error instead of a warning
-
- Closed
-
-
MDEV-33670 Redo log overwritten/corrupted
-
- Confirmed
-
-
MDEV-34566 InnoDB: Crash recovery is broken due to insufficient innodb_log_file_size (but wasn't in crash recovery)
-
- Closed
-
Related to
MDEV-14425, we plan to change the way how the redo log is written.As part of introducing a dedicated log writer thread, we can remove this limitation altogether, and have the dedicated thread initiate log checkpoints when necessary.