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

MariaDB 10.5 does not do idle checkpoint (regression)

    XMLWordPrintable

Details

    Description

      MariaDB 10.5 does not checkpoint as I would expect (i.e same as in MariaDB 10.4 or PS 5.7 ) .

      Attached is the graph of how MariaDB 10.5 checkpoints, i.e it let's redo log get to max checkpoint age, then checkpoints everything , then start over.
      It is easily repeatable by creating a new instance from scratch with all the defaults and insert a few records, checking that checkpoint age does not move.

      SEIS On MariaDB :
      Log sequence number 1850969
      Log flushed up to 1850969
      Pages flushed up to 1846760
      Last checkpoint at 1846748

      SEIS on PS 5.7:
      Log sequence number 4441325019
      Log flushed up to 4441325019
      Pages flushed up to 4441325019
      Last checkpoint at 4441325010

      It can be seen that "Last checkpoint at xxxx" is close to LSN on PS, but on MariaDB 10.5 it will remain with a fixed value until max checkpoint age.

      In the attachment it can be seen that every ~4 hours the redo logs gets full, does an almost complete checkpoint and starts again. This causes an stall of a few seconds while the disks (which luckily are fast) do the checkpoint

      On MariaDB 10.4 this does not happen and I have also compared configuration between 10.4 and 10.5 and could not find anything.

      This other bug report MDEV-25093 mentions that any flushing is skipped but it seems something still broken.

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              ctutte carlos tutte
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.