[MDEV-24526] binlog rotate via FLUSH LOGS may obsolate binlog file for recovery too early - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 10.2.38, 10.3.29, 10.4.19, 10.5.10
Component/s: Replication
Labels:
- binlog_checkpoint

Description

There's a race between FLUSH LOGS and binlog-group commit for Binlog-checkpoint notification which must be done *after* the committed group transactions' affected
data are flushed to disk. However the notification may happen before that fore the reason
FLUSH LOGS handler does to acquire necessary mutexes.

A test case follows with a patch to be committed soon.

Attachments

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

_binlog_checkpoint_stress.test
2 kB
2021-01-07 13:21

Issue Links

relates to

MDEV-24530 binlog-optimize-thread-scheduling=0 case of binlog rotate via FLUSH LOGS may obsolate binlog file too eary

Open

MDEV-24302 RESET MASTER hangs as Innodb does not report on binlog checkpoint

Closed

MDEV-28948 FLUSH BINARY LOGS waits/hangs on mysql_mutex_unlock(&LOCK_index) forever

Closed

Activity

People

Assignee:: Andrei Elkin

Reporter:: Andrei Elkin

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2021-01-05 13:15

Updated:: 2022-06-27 12:10

Resolved:: 2021-04-21 13:27

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

1.75d

Git Integration

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