You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
replicators: Add a timeout to MySQL replication connections
We enable heartbeats on the source (every second), and if we receive no
packet for five seconds, we close the connection and reconnect.
Release-Note-Core: MySQL replication now uses heartbeats to detect
stale, half-closed connections and reconnect to the server.
Fixes: REA-5870
Change-Id: I791074209980a5eb765dcdf0f432549c254f55b3
Reviewed-on: https://gerrit.readyset.name/c/readyset/+/9988
Tested-by: Buildkite CI
Reviewed-by: Michael Zink <michael.z@readyset.io>
| EventType::FORMAT_DESCRIPTION_EVENT // A descriptor event that is written to the beginning of each binary log file. This event is used as of MySQL 5.0; it supersedes START_EVENT_V3.
1217
1239
| EventType::STOP_EVENT // Written when mysqld stops
1218
1240
| EventType::INCIDENT_EVENT // The event is used to inform the slave that something out of the ordinary happened on the master that might cause the database to be in an inconsistent state.
1219
-
| EventType::HEARTBEAT_EVENT => {} // The event is originated by master's dump thread and sent straight to slave without being logged. Slave itself does not store it in relay log but rather uses a data for immediate checks and throws away the event.
0 commit comments