[MDEV-38730] innodb_log_file_mmap=ON does not work on AMD64, ARMv8, POWER - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.11, 11.4, 11.8
Fix Version/s: 10.11.17, 11.4.11, 11.8.7
Component/s: Storage Engine - InnoDB
Labels:
Environment:
GNU/Linux on AMD64, ARMv8 or POWER

Bug Category:
Related to performance
Release Note Summary:
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

MDEV-34062 mariadb-backup --backup is extremely slow at copying ib_logfile0

Closed

MDEV-37949 Implement innodb_log_archive

Closed

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Assigned for Implementation:: Marko Mäkelä

Assigned for Review:: Thirunarayanan Balathandayuthapani

Assigned for Testing:: Saahil Alam

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2026-02-02 13:42

Updated:: 2026-06-15 13:55

Resolved:: 2026-02-04 08:58

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

1d 1.75h

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.