Multi Master Replication (MMR) Stops Without Any Particular Error Message - Error_code: 1756
(Doc ID 1577463.1)
Last updated on FEBRUARY 08, 2019
Applies to:
MySQL Server - Version 5.6 to 5.7 [Release 5.6 to 5.7]Information in this document applies to any platform.
MMR - Multi Master Replication
Symptoms
Error log has following messages without any other related errors:
2013-08-08 06:38:00 6156 [Note] Worker 0 is exiting: killed 0, error 0, running_status 2
2013-08-08 06:38:00 6156 [ERROR] Slave SQL: ... The slave coordinator and worker threads are stopped, possibly leaving data in inconsistent state. A restart should restore consistency automatically, although using non-transactional storage for data or info tables or DDL queries could lead to problems. In such cases you have to examine your data (see documentation for details). Error_code: 1756
2013-08-08 06:38:00 6156 [ERROR] Slave SQL: ... The slave coordinator and worker threads are stopped, possibly leaving data in inconsistent state. A restart should restore consistency automatically, although using non-transactional storage for data or info tables or DDL queries could lead to problems. In such cases you have to examine your data (see documentation for details). Error_code: 1756
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 |
| Cause |
| Solution |
| References |