0 views collected around this technical thread.
In MySQL 5.7, using REPLACE INTO on a table that has an auto‑increment primary key and an extra unique index can cause the master and slave AUTO_INCREMENT counters to diverge, leading to duplicate‑key errors after failover, a bug mitigated by upgrading to MySQL 8.0, manual counter fixes, or avoiding REPLACE INTO.
This article explains MySQL master‑slave replication, covering its three modes (asynchronous, semi‑synchronous, and fully synchronous), the underlying binary‑log mechanism, key replication threads, configuration steps, and includes a promotional notice for an upcoming live career‑development session.
This article provides a detailed source‑code walkthrough of MySQL 8.0.33’s two‑phase commit process, explaining the Prepare and Commit stages, internal structures such as binlog queues, GTID generation, redo‑log flushing, sync handling, and the interactions between InnoDB and the binary log.
This article compiles eight classic MySQL error scenarios—including forgotten passwords, case‑sensitivity mismatches, Windows service startup failures, export/import restrictions, excessive connections, full binary logs, and primary‑key replication conflicts—along with detailed troubleshooting steps, configuration tweaks, and command‑line solutions to help database practitioners resolve them efficiently.
This article examines how MySQL slaves recover their replication state in GTID‑based and binary‑log‑file‑position scenarios, identifies unsafe factors that can cause crash‑unsafe behavior, and explains how enabling relay_log_recovery=on mitigates these risks while outlining remaining limitations.
This article explains MySQL GTID (Global Transaction Identifier), covering its composition, lifecycle, how GTIDs are generated during commit, the mechanisms that maintain GTID state, and practical examples that illustrate GTID behavior in replication scenarios.
This article explains MySQL's three‑layer logical architecture, the roles of binary log, redo log, and undo log, how they interact during data updates, and the configuration options that affect durability and performance.
This article explains MySQL's three‑layer logical architecture, the roles of redo, undo, and binary logs, how they interact with the buffer pool and crash recovery, and provides practical commands for managing slow query, general, and error logs.
This article explains MySQL's built‑in replication mechanism, covering its purpose, supported replication formats, step‑by‑step master‑slave configuration, common topologies, troubleshooting techniques, and practical SQL commands for setting up and maintaining reliable data distribution and high availability.
This article explains the role of MySQL binary logs for replication and point‑in‑time recovery, outlines four practical cleanup techniques—including reset master and purge commands—and demonstrates how to switch logs using flush operations while showing relevant command outputs and screenshots.
This article explains what MySQL master‑slave replication is, outlines its benefits, details the underlying mechanisms and event types, and provides a comprehensive, command‑line tutorial for configuring both master and slave servers, complete with code snippets and illustrative diagrams.
This article explains MySQL’s six log files, focusing on the redo log, undo log, and binary log, detailing their purposes, contents, generation and release timing, associated physical files, configuration parameters, and their roles in transaction durability and replication.
This article explains the three most important MySQL log types—redo log, undo log, and binary log—detailing their purposes, contents, creation and release timing, related configuration parameters, physical files, and how they interact with transaction processing and replication.
This article introduces the open‑source infobin utility for parsing MySQL binary logs, explains how it detects long‑running and large transactions, measures event generation speed, aggregates per‑table DML events, and demonstrates its usage with sample commands and output, offering a faster alternative to mysqlbinlog.
This guide explains the complete process of configuring MySQL master‑slave replication on two CentOS machines, covering prerequisite setup, enabling binary logging, creating a replication user, capturing binlog coordinates, configuring the slave, and verifying successful synchronization.
gh‑ost is a lightweight, trigger‑free, Go‑based online MySQL schema‑change tool that reads binary logs, applies alterations to temporary tables, and offers pauseable, auditable, and dynamically controllable migrations via socket commands, supporting master‑only, replica‑assisted, or replica‑testing modes and used extensively at GitHub.