[MDEV-28766] MDEV-28111 breaks innodb_flush_log_at_trx_commit=2 - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 10.8.3, 10.9.1
Fix Version/s: 10.10.0, 10.8.4, 10.9.2
Component/s: Storage Engine - InnoDB
Labels:
None
Environment:
Linux

Description

~~MDEV-28111~~ and specifically commit c4c88307091 breaks the meaning of innodb_flush_log_at_trx_commit = 2 by enabling O_DIRECT for the redo log.

O_DIRECT should not be used when innodb_flush_log_at_trx_commit = 2 is set. Since this variable is dynamic, it has not only to be checked at server startup, but each time the variable is written to.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

sysbench_insert.png
2022-06-07 13:37
6 kB
Axel Schwenke
sysbench_insert2.png
2022-06-09 15:50
7 kB
Axel Schwenke
sysbench_insert3.png
2022-06-09 16:54
11 kB
Axel Schwenke

Issue Links

is caused by

MDEV-28111 Redo log writes are being buffered on Linux for no good reason

Closed

relates to

MDEV-30136 Map innodb_flush_method to new settable Booleans innodb_{log,data}_file_{buffering,write_through}

Closed

MDEV-31642 Upgrade from 10.7 or earlier may crash if innodb_log_file_buffering=OFF

Closed

MDEV-24854 Change innodb_flush_method=O_DIRECT by default

Closed

MDEV-33894 MariaDB does unexpected storage read IO for the redo log

Closed

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Axel Schwenke

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2022-06-07 13:11

Updated:: 2024-04-12 10:21

Resolved:: 2022-06-14 16:07

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

5d 5.25h

Git Integration

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