The Monday morning report: four hours of MySQL replica lag
Four hours of lag on a MySQL replica in a logistics system. How we diagnosed it, why Seconds_Behind_Master lies, and what actually fixed it.

Four hours of lag on a MySQL replica in a logistics system. How we diagnosed it, why Seconds_Behind_Master lies, and what actually fixed it.

A real MySQL 8.0.34→8.0.45 patching workflow: broken views blocking mysqldump, GTID warnings, replica role check, and RPM upgrade order on RHEL 8.

MySQL binary log: management, retention and point-in-time recovery. Real case of a server with disk at 95% and 180 GB of binlogs in six months.

3-node MySQL Galera Cluster for high availability: synchronous replication, quorum, SST/IST. Full configuration against single point of failure.

Oracle Data Guard 19c: migration from single instance after a 6-hour outage. DR architecture, primary/standby, automatic switchover.

3-node MySQL Group Replication: migrating binary logs to a dedicated volume without losing quorum. Real case with filesystem at 92%.
Start typing to search…
Select a result to see the preview