[MDEV-27917] Some redo log diagnostics is always reported as 0 Created: 2022-02-22  Updated: 2022-02-22  Resolved: 2022-02-22

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.8.1
Fix Version/s: 10.9.0, 10.8.3

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-14425 Change the InnoDB redo log format to ... Closed
relates to MDEV-21534 improve locking/waiting in log_write_... Closed

 Description   

The InnoDB monitor counter log_sys.n_log_ios was almost removed in MDEV-14425. This counter was rather meaningless already since MDEV-21534 introduced a redo log group commit mechanism, and on the persistent memory interface there are no file system calls that could be counted. With MDEV-14425, the only case when the counter is updated is when the log file is being read during crash recovery.

Some related InnoDB monitor output in log_print() as well as the information_schema.innodb_metrics counter log_num_log_io are best removed.
Generated at Thu Feb 08 09:56:36 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.