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

innodb_max_purge_lag is documented as being in milliseconds, not microseconds

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • N/A
    • N/A
    • Documentation
    • None

    Description

      Via Marko:
      Related to MDEV-29401, Axel noted that innodb_max_purge_lag is documented as being in milliseconds, while in reality it is in microseconds.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29401 InnoDB history list length increased in 10.6 compared to 10.5 for the same load

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

          Activity

            Ascending order - Click to sort in descending order
            TheWitness Larry Adams added a comment -

            Where is the documentation? I searched google for this setting, and could not find it.

            TheWitness Larry Adams added a comment - Where is the documentation? I searched google for this setting, and could not find it.
            greenman Ian Gilfillan added a comment -

            https://mariadb.com/kb/en/innodb-system-variables/#innodb_max_purge_lag - the full reference is on https://mariadb.com/kb/en/full-list-of-mariadb-options-system-and-status-variables/

            greenman Ian Gilfillan added a comment - https://mariadb.com/kb/en/innodb-system-variables/#innodb_max_purge_lag - the full reference is on https://mariadb.com/kb/en/full-list-of-mariadb-options-system-and-status-variables/
            TheWitness Larry Adams added a comment -

            Yea found it. This whole constellation of settings around purging the undo/redo logs (aka ibdata1) is poorly documented. I would like a write-up on how to maximize the flushing rate on NVMe systems with 100+ cores and dozen TB databases. It's just not there.

            TheWitness Larry Adams added a comment - Yea found it. This whole constellation of settings around purging the undo/redo logs (aka ibdata1) is poorly documented. I would like a write-up on how to maximize the flushing rate on NVMe systems with 100+ cores and dozen TB databases. It's just not there.

            People

              greenman Ian Gilfillan
              greenman Ian Gilfillan
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.