[MDEV-27251] SLAVE replication breaks on mariadb version 10.6.5 Created: 2021-12-13  Updated: 2023-09-20  Resolved: 2023-09-20

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.6.5
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Yalwa Sysops Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: replication
Environment:

Operating system: openSUSE Tumbleweed
Mariadb version: 10.6.5
Kernel version: 5.10.80



 Description   

SLAVE replication breaks with mariadb master running on version 10.6.5

We recently updated our mariadb master from 10.5.10 to 10.6.5 and since then started experiencing some random replication failure on our slave nodes.

However Slave nodes running version 10.6.5 but replicating to older 10.5.10 mariadb master works just fine.

Replication breaks around 4 times now (exactly at a binlog offset position 4) since the last 5 days after upgrading master to version 10.6.5.
In case it helps: We have multiple clients connecting to the master node and experiencing similar problem.

Logs during two such incidents as below:


2021-12-09 19:16:23 3399833 [ERROR] Read invalid event from master: 'Found invalid event in binary log', master could be corrupt but a more likely cause of this is a bug
2021-12-09 19:16:23 3399833 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Internal MariaDB error code: 1595
2021-12-09 19:16:23 3399833 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000004', position 4, master xxxx:3306



2021-12-13 14:00:34 4 [ERROR] Read invalid event from master: 'Found invalid event in binary log', master could be corrupt but a more likely cause of this is a bug
2021-12-13 14:00:34 4 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Internal MariaDB error code: 1595
2021-12-13 14:00:34 4 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000121', position 4, master xxxx:3306


Affected Mariadb version on master : 10.6.5
——

  1. MASTER configuration
    [mysqld]
    log-bin=mysql-bin
    log-slave-updates
    binlog-format=STATEMENT
    expire_logs_days=3

Kindly request your support here !! Thanks in advance!



 Comments   
Comment by Yalwa Sysops [ 2021-12-23 ]

We are seeing the same behaviour happening at-least 10 times now.
And again: (exactly at a binlog offset position 4)

Looking forward to some support here . Thanks !

Comment by Patrick Schaaf [ 2022-08-31 ]

For the record, with an openSUSE package update early March this year, still mariadb 10.6.5, I don't know what changed within it - the situation resolved itself, in that we never saw that replication breakage again the last 6 months.

Generated at Thu Feb 08 09:51:31 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.