Row-Based Replication of Table with Temporal Column Causes High Memory Usage in MySQL 5.6 Earlier Than 5.6.21; Out of Memory (OOM)
Last updated on MARCH 08, 2017
Applies to:MySQL Server - Version 5.6 to 5.6 [Release 5.6]
Information in this document applies to any platform.
When attempting to replicate a table with a column using a temporal data type, the replication slave uses a large amount of memory and may crash due to an out of memory condition.
The following conditions holds true:
- The replication slave is MySQL 5.6 patch release 5.6.20 or earlier.
- The master's table was created in MySQL 5.5 or earlier (but the master may have been upgraded to MySQL 5.6).
- The slave's table was created in MySQL 5.6.
This issue can start to occur after:
- upgrading the slave to MySQL 5.6
- a table with a temporal column was rebuild on the replication slave
- when replicating from a MySQL 5.5 master to a MySQL 5.6 slave, a temporal data type column was added to a table or a new table with a temporal data type column was created
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