[MDEV-31133] MariaDB Slave crash and cannot restart - Jira

XML

Word

Printable

Details

Type: Bug
Status: Open (View Workflow)
Priority: Critical
Resolution: Unresolved
Affects Version/s: 10.4.28
Fix Version/s: None
Component/s: Replication
Labels:
None
Environment:

Hide
Rocky Linux release 8.7 on 4 servers with MariaDB 10.4 master / slave replication
1 MariaDB Server 10.4.24 as master
1 MariaDB Server 10.4.24 as slave
1 MariaDB Server 10.4.27 as slave
1 MariaDB Server 10.4.28 as slave (the one that crash)

Show
Rocky Linux release 8.7 on 4 servers with MariaDB 10.4 master / slave replication 1 MariaDB Server 10.4.24 as master 1 MariaDB Server 10.4.24 as slave 1 MariaDB Server 10.4.27 as slave 1 MariaDB Server 10.4.28 as slave (the one that crash)

Description

Slave crash during replication and crash again and again at restart. I could restart with innodb_force_recovery=3, reset slave but mariadb crash as soon as I restart without innodb_force_recovery.
Downgrading to MariaDB 10.4.27 solved the problem.

attached is the log of the first crash and one restart crash

Attachments

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

first-crash.log
2023-04-26 13:28
6 kB
Maurice Gasco
other-crash.log
2023-04-26 13:28
9 kB
Maurice Gasco

Issue Links

relates to

MDEV-23713 Replication stops with "Index for table is corrupt", table with HASH index, assertion: !cursor->index->is_committed() fails in row_ins_sec_index_entry_by_modify

Closed

Activity

People

Assignee:: Unassigned

Reporter:: Maurice Gasco

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2023-04-26 13:33

Updated:: 2023-04-26 14:39

Git Integration

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