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

History list is not shrunk unless there is a pause in the workload

Details

    Description

      While testing MDEV-32050 and its follow-up changes MDEV-33009 and MDEV-33112, axel pointed out that the InnoDB history list is not being shrunk during a workload.

      Some initial debugging indicates that the purge_truncation_task (which was added in MDEV-32050) is being invoked but it is not doing anything. Also, the purge_sys.view is advancing; there are no old read views that would block the purge of history. Throttling the Sysbench workload for a few seconds would allow the history list to shrink immediately.

      Attachments

        1. 10.6-MDEV-33213.pdf
          107 kB
          Axel Schwenke
        2. 12x5.pdf
          58 kB
          Axel Schwenke
        3. 24x5_high_threads_pausing.pdf
          59 kB
          Axel Schwenke
        4. 24x5_high_threads.pdf
          56 kB
          Axel Schwenke
        5. 24x5.pdf
          59 kB
          Axel Schwenke
        6. no_pause.png
          36 kB
          Axel Schwenke
        7. with_pause.png
          47 kB
          Axel Schwenke

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33464 Crash when innodb_max_undo_log_size is set to innodb_page_size*4294967296

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34259 Optimization in row_purge_poss_sec Function for Undo Purge Process

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30628 10.6 performance regression with sustained high-connection write-only OLTP workload (55-80% degradation)

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31676 Innodb history length keeps growing

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32050 UNDO logs still growing for write-intensive workloads

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33009 Server hangs for a long time with innodb_undo_log_truncate=ON

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33112 innodb_undo_log_truncate=ON is blocking page writes

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33315 InnoDB history length and undo tablespace files keep growing

          • Major - Major loss of function.
          • Closed

          Activity

            Transition Time In Source Status Execution Times
            Marko Mäkelä made transition -
            Open In Progress
            		2h 51m 1
            Marko Mäkelä made transition -
            In Progress In Testing
            		23h 55m 1
            Matthias Leich made transition -
            In Testing Stalled
            		4d 5h 49m 1
            Marko Mäkelä made transition -
            Stalled In Review
            		9h 18m 1
            Marko Mäkelä made transition -
            In Review Closed
            		1d 4h 56m 1

            People

              marko Marko Mäkelä
              marko Marko Mäkelä
              Votes:
              1 Vote for this issue
              Watchers:
              11 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.