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

Remove dummy tablespace for the redo log

Details

    Description

      In InnoDB, redo log file operations unnecessarily go through the fil_io() API. It would be cleaner to just have the log file descriptors straight inside log_sys.log.

      Most redo log writes are synchronous. The only exception is writing the checkpoint header block, which uses asynchronous I/O. It might be better to dedicate the io_handler_thread() for data file operations only, and not let them deal with the redo log checkpoint write completion.

      Attachments

        Issue Links

          blocks

          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-16526 Overhaul the InnoDB page flushing

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-21382 use fdatasync() for redo log where appropriate

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13542 Crashing on a corrupted page is unhelpful

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31170 Document MDEV-18115, Remove dummy tablespace for the redo log

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MDEV-26603 asynchronous redo log write

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31124 Innodb_data_written miscounts doublewrites

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Transition Time In Source Status Execution Times
            Eugene Kosov (Inactive) made transition -
            Open In Progress
            		37d 11h 25m 1
            Eugene Kosov (Inactive) made transition -
            In Progress In Review
            		316d 7h 37m 1
            Marko Mäkelä made transition -
            In Review Stalled
            		2d 11h 56m 1
            Eugene Kosov (Inactive) made transition -
            Stalled Closed
            		9d 8h 41m 1

            People

              kevg Eugene Kosov (Inactive)
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.