Replica Performance Too Slow With Row Based Events For Table Without Primary Key
(Doc ID 2271864.1)
Last updated on SEPTEMBER 04, 2023
Applies to:
MySQL Server - Version 5.5 and laterMySQL Cluster - Version 7.2 and later
Information in this document applies to any platform.
Symptoms
Disclaimer: Starting from v8.0, some terms have been deprecated. Older releases will only use the deprecated terminology, and new releases will only use new terminology. Please see https://dev.mysql.com/doc/mysqld-version-reference/en/ for a complete list of those changes, and in which minor versions it happened.
The replica SQL thread cannot keep up while processing row based events from the source's binary log. For example:
Changes
Several changes may cause this to start happening, for example:
- A new table without a primary key has been added to the system.
- The primary key was removed from an existing table.
- The binlog_format option was changed from STATEMENT to MIXED or ROW or from MIXED to ROW. See also <Note 1507802.1>.
- Upgrading from MySQL 5.6 or earlier to MySQL 5.7 or later while using the deafult value for binlog_format as the default changed from STATEMENT to ROW.
- The workload changed with binlog_format = MIXED. When the format is set to MIXED, MySQL will automatically use the row based format, if the statement is considered potential non-deterministic.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |