[MDEV-27295] MariaDB 10.5 does not do idle checkpoint (regression). Marked as fixed on 10.5.13 but it is not - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.5.13
Fix Version/s: N/A
Component/s: Documentation, Storage Engine - InnoDB
Labels:
None

Description

Hi!

I upgraded to 10.5.13 to fix ~~MDEV-26860~~ but it is still not fixed.

To reproduce, start a server with the defaults and check "show engine innodb status;" i.e get the following outputs:

Log sequence number 1851090
Log flushed up to 1851090
Pages flushed up to 1851090
Last checkpoint at 1851078

Then do some inserts on any table and check SEIS again:

Log sequence number 1852662
Log flushed up to 1852662
Pages flushed up to 1851090
Last checkpoint at 1851078

it can be seen that checkpoint is yet not moving forward. If monitoring with PMM, the graphs looks like a "saw tool" like on the bug report from ~~MDEV-26860~~

Attachments

Issue Links

relates to

MDEV-23855 InnoDB log checkpointing causes regression for write-heavy OLTP

Closed

MDEV-24537 innodb_max_dirty_pages_pct_lwm=0 lost its special meaning

Closed

MDEV-24949 Enabling idle flushing (possible regression from MDEV-23855)

Closed

MDEV-26860 MariaDB 10.5 does not do idle checkpoint (regression)

Closed

Activity

People

Assignee:: Ian Gilfillan

Reporter:: carlos tutte

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Dates

Created:: 2021-12-17 12:56

Updated:: 2023-11-05 19:35

Resolved:: 2022-06-29 10:14

Git Integration

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