This error is related to the Replication IO_Thread being stopped with Error Number 1236. The error Message 1236 can be triggered by many reason i will try my best to cover the most common reasons. Please keep in mind i'm using GTID replication, in case you're using Binary log file/position replication some solution to fix …
Continue reading Fix MySQL Async replication Error 1236 within GTID Replication
when one node was already down in a cluster of 3 nodes, which mean you currently have 2/3 nodes up and running, that can result to a non quorum state and create a split brain situation. When a split brain situation occur you will have the following error message while trying to run any query …
What’s GTID A Global Transaction Identifier (GTID) is Unique ID created and associated with each transaction committed on the primary database. Format of GTID GTID=source_id:transaction_id Where: The source_id identifies the originating serverThe transaction_id is a sequence number determined by the order in which the transaction was executed Example: 4a7d0f2e-0985-11e9-a0f0-005056a474e3:1-40093708 Skipping Transaction When GTIDs Are Enabled …
Continue reading How to skip transaction on replica when GTID replication is broken
What’s GTID A Global Transaction Identifier (GTID) is Unique ID created and associated with each transaction committed on the primary database. Format of GTID GTID=source_id:transaction_id Where: The source_id identifies the originating serverThe transaction_id is a sequence number determined by the order in which the transaction was executed Example: 4a7d0f2e-0985-11e9-a0f0-005056a474e3:1-40093708 Why Go for GTID Replication It’s …
Continue reading Migrate from Files based replication to GTID Without downtime in 5.7+
I did the following to restore the failed node from backup and able to recover the cluster state. 1)Below is the status of the cluster when one of the nodes failed (node3:3306). MySQL node3:3306 ssl JS > c.status() { "clusterName": "myCluster", "defaultReplicaSet": { "name": "default", "primary": "node1:3306", "ssl": "REQUIRED", "status": "OK_NO_TOLERANCE", "statusText": "Cluster is NOT …
In a Master/Slave replication data consistency is a biggest concern and is very easy to break your replication with issues such as duplicate keys, missing rows , accidental writes from application connected to the slave or even by a DBA connected to the slave 🙁 “yes things happen” . 1. read_only When the read_only system variable is enabled, the server …
Continue reading Best practice to avoid duplicate entry errors on the slave
Normally MySQL replication will stop whenever there is an error running a query on the slave. This happens in order for us to be able to identify the problem and fix it, and keep the data consistent with the mater that has sent the query. You can skip such errors, even if this is not …
Requirements This topic assumes that you have user with sudo privileges and have MySQL installed on both server(Master & Slave). If you do not have MySQL server installed, you can install it with this topic . My Master IP address is 192.168.147.12, and my slave is at 192.168.147.16. You must also make sure you have …
Continue reading Setup a simple MySQL Master Slave Replication
Mikael HOUNDEGNON MySQL Wall 