[MDEV-32757] innodb_undo_log_truncate=ON is not crash safe - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 10.5, 10.6, 10.11, 11.0(EOL), 11.1(EOL), 11.2, 11.3(EOL)
Fix Version/s: 10.5.24, 10.6.17, 10.11.7, 11.0.5, 11.1.4, 11.2.3, 11.3.2
Component/s: Storage Engine - InnoDB
Labels:
- recovery
- regression

Description

As noted in ~~MDEV-32681~~, the invocation of buf_page_t::clear_oldest_modification() in trx_purge_truncate_history() is unsafe. The buf_flush_page_cleaner() thread may advance the checkpoint before mtr_t::commit_shrink() has finished executing. This may cause a previously committed transaction to be treated as uncommitted. The server could crash or hang while trying to roll back the "uncommitted" transaction. With the data.tar.xz that is attached to ~~MDEV-32681~~, the rollback would try to free an undo log page multiple times and possibly end up in an infinite loop.

Attachments

Issue Links

is caused by

MDEV-26445 innodb_undo_log_truncate is unnecessarily slow

Closed

relates to

MDEV-33009 Server hangs for a long time with innodb_undo_log_truncate=ON

Closed

MDEV-32681 Test case innodb.undo_truncate_recover frequent failure

Closed

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2023-11-10 07:49

Updated:: 2024-11-08 19:09

Resolved:: 2023-11-15 13:01

Git Integration

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