Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-27917

Some redo log diagnostics is always reported as 0

Details

    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.

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-14425 Change the InnoDB redo log format to reduce write amplification

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Task - A task that needs to be done. MDEV-21534 improve locking/waiting in log_write_up_to

          • Major - Major loss of function.
          • Closed

          Activity

            Transition Time In Source Status Execution Times
            Marko Mäkelä made transition -
            Open Closed
            		28m 38s 1

            People

              marko Marko Mäkelä
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.