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

innodb_log_file_mmap=ON does not work on AMD64, ARMv8, POWER

    XMLWordPrintable

Details

    • Related to performance
    • The setting innodb_log_file_mmap=ON did not enable memory-mapped log file parsing.

    Description

      The setting innodb_log_file_mmap=ON did not have the desired effect on systems where the persistent memory interface is available, that is, Linux targeting AMD64, ARMv8 or POWER. On those systems, we’d implement special handling to treat any file in /dev/shm as if it were persistent memory. This special handling would wrongly refuse to enable memory-mapped log recovery if the initial attempt to map persistent memory failed.

      I found this anomaly file testing MDEV-37949.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34062 mariadb-backup --backup is extremely slow at copying ib_logfile0

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MDEV-37949 Implement innodb_log_archive

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

          Activity

            People

              marko Marko Mäkelä
              marko Marko Mäkelä
              Marko Mäkelä Marko Mäkelä
              Thirunarayanan Balathandayuthapani Thirunarayanan Balathandayuthapani
              Saahil Alam Saahil Alam
              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.