MySQL Bugs: #112218: relay log event crc check failed on arm platform

Bug #112218	relay log event crc check failed on arm platform
Submitted:	30 Aug 2023 8:06	Modified:	7 Oct 2023 14:36
Reporter:	Allen Iverson	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	8.0.28	OS:	Linux
Assigned to:	MySQL Verification Team	CPU Architecture:	ARM
Tags:	arm, corruption, crc check, relay

Description:

MySQL 8.0 slave under arm architecture occasionally encounters replication interruptions. it seems relay log event readed by sql thread is corrupted ,according to MySQL error log. However, the relay log can be parsed normally using mysqlbinlog; it can also recover normally after restarting the sql thread.

error log below:
```
2023-08-25T21:32:08.289746+08:00 1386201 [ERROR] [MY-010596] [Repl] Error reading relay log event for channel '': Event crc check failed! Most likely there is event corruption.
2023-08-25T21:32:08.289813+08:00 1386201 [ERROR] [MY-013121] [Repl] Slave SQL for channel '': Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, the server was unable to fetch a keyring key required to open an encrypted relay log file, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: MY-013121
2023-08-25T21:32:08.291711+08:00 1386201 [ERROR] [MY-010586] [Repl] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'binlog.006892' position 367290759
2023-08-25T21:45:17.956168+08:00 16728861 [Note] [MY-010581] [Repl] Slave SQL thread for channel '' initialized, starting replication in log 'binlog.006892' at position 367290759, relay log 'binlog/relay.014693' position: 367290929
```

How to repeat:
It happens occasionally, don’t know how to repeat

Hi,

More data is needed
 - have you tried 8.0.34 or 8.1 ?
 - what build are you using? 
 - what OS are you running this build on?
 - what hardware are you running this build on?

Thanks

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

we encountered the same problem on ARMky10,mysql8.0.25...

Can you please try latest 8.0? as really not much we can do to make 8.0.25 work.