Slave servers with query cache enabled crash with memory corruption errors
Last updated on DECEMBER 24, 2014
Applies to:MySQL Server - Version 5.1 to 5.6 [Release 5.1 to 5.6]
Information in this document applies to any platform.
Slaves with query cache enabled, replicating Mixed or Statement based events are seen randomly crashing, often with glibc memory corruption errors. Note: As DDL statements are always using the Statement based format these can trigger the memory corruption even when using Row based replication.
Affected versions are:
- 5.1: 5.1.60, 5.1.61, 5.1.62, 5.1.63, 5.1.64
- 5.5: 5.5.18, 5.5.19, 5.5.20, 5.5.21, 5.5.22, 5.5.23, 5.5.24, 5.5.25
Common symptoms include messages like this in the error logs:
The backtrace will show the crash happening in various code locations, typically involving the query cache and parser.
For existing slaves the issue will typically happen after either:
- Upgrading to one of the above mentioned versions.
- Enabling the query cache.
- Changing replication format to Mixed or Statement.
- Running DDL statements.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms