MySQL servers can trigger alarming disk‑space warnings even when the data directory is small, because unchecked binary logs rapidly consume storage; this article explains the log’s purpose, why it grows, how to diagnose the issue, and provides step‑by‑step cleanup, configuration, replication, monitoring, and recovery best practices.
The article explains how MySQL determines whether a statement should be recorded in the binary log under ROW format, detailing the check_table_binlog_row_based function, the cached_row_logging_check flag, OPTION_BIN_LOG, and various scenarios—such as temporary tables, replication filters, no‑replicate tables, session settings, and internal operations—where binlog entries are omitted.
This article explains how MySQL binary logs can rapidly consume disk space, analyzes the root causes such as log format and workload, provides step‑by‑step diagnostics, and offers practical cleanup, configuration, replication, monitoring, and recovery strategies to prevent and resolve the issue.
This comprehensive guide explains MySQL binary log fundamentals, why they consume disk space, how to diagnose growth issues, and provides step‑by‑step cleanup, configuration, monitoring, and recovery strategies for both primary and replica servers.
This article explains MySQL master‑slave replication, covering its purpose for high availability and read‑write separation, typical one‑master‑multiple‑slaves architecture, the binlog‑based synchronization mechanism, and the roles of the master’s dump thread and the slave’s I/O and SQL threads.
This article explains MySQL replication architecture, detailing how binary logs are transferred, the roles of dump, I/O receiver, and SQL apply threads, the metadata tables they use, and key system variables for optimizing replication performance and durability.
This guide explains MySQL logging types—including error, general, binary, and slow query logs—their default settings, how to enable or modify them, how to view and interpret log contents, and practical commands for backup, recovery, and cleanup.
This article explains why MySQL 8.0 replication to a 5.7 slave fails because of the new utf8mb4_0900_ai_ci collation, analyzes the root causes, and provides step‑by‑step configuration and SQL‑based solutions to ensure a smooth upgrade without data loss.
This guide explains MySQL’s error, general, binary, and slow query logs, covering default settings, how to enable or modify them, binary log formats and recovery procedures, as well as tools for analyzing slow queries, providing a comprehensive reference for database administrators.
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 explains MySQL's fault‑tolerance mechanisms, covering data persistence, storage engines, the binary, redo, and undo logs, WAL, two‑phase commit, and step‑by‑step recovery procedures for accidental data loss or crashes.
This article explains the purpose, flushing mechanisms, and key differences of MySQL's redo log, binary log, and undo log, highlighting how they ensure durability, support recovery, and enable atomic rollback in InnoDB.
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.
A detailed post‑mortem of a MySQL dual‑master cluster failure caused by a missing mysql-bin.index file, showing step‑by‑step diagnostics, container logs, replication position fixes, and preventive measures for high‑availability deployments.
This article explains MySQL replication fundamentals, binary log mechanics, master‑slave roles, configuration steps, and the various replication types—including asynchronous, semi‑synchronous, multi‑source, and delayed replication—while providing practical commands and code examples for reliable high‑availability setups.
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 guide explains MySQL binary log fundamentals, the replication architecture, step‑by‑step configuration of master‑slave instances, essential commands, and troubleshooting tips for common replication problems such as lag, errors, and security settings.
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 provides a comprehensive guide to MySQL replication, covering built‑in replication types, the three‑step replication workflow, detailed master‑slave configuration commands, topology options, cloning methods, binlog formats, replication files, filtering, and common error scenarios with solutions.
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 guide demonstrates a complete MySQL disaster‑recovery workflow that combines LVM snapshot technology with binary‑log point‑in‑time recovery, allowing you to restore a dropped database by creating a snapshot, extracting it, and replaying binlog events up to the failure moment.
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.
This article explains the purpose, content, generation timing, storage files, and release mechanisms of MySQL's redo log, undo log, and binary log, highlighting their roles in transaction durability, MVCC, and replication, and clarifying key differences and interactions among them.
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.
When a sales employee's workflow records vanished after a WeChat ID change, the team traced the deletion to MySQL binary logs, extracted the relevant log entries, and used bulk UPDATE statements to replace the old user_id with the new one, fully restoring the missing data.
This guide explains how to collect replication status, analyze MySQL error logs and binary logs, compare master and slave configurations, and troubleshoot common replication failures such as GTID mismatches, missing binlogs, and conflicting statements in UDB environments.
Learn how to reduce MySQL replication delay by examining the three key stages—binary log writing, log transmission, and slave SQL replay—and applying tactics such as breaking large transactions, ignoring unnecessary databases, and enabling multi‑threaded replication in MySQL 5.7.
In a MySQL 5.7 GTID setup with dual masters, a network glitch caused the slave to switch masters, leading to the ER_MASTER_HAS_PURGED_REQUIRED_GTIDS error because the new master had purged GTIDs the slave still needed, and the article explains the root cause and step‑by‑step fix.
This article uses the Golden Circle framework to explore MySQL replication, detailing its definition, benefits such as scaling and fault tolerance, the underlying mechanisms involving binary logs and IO/SQL threads, and addressing common practical questions through a self‑Q&A format.
This article explains MySQL replication fundamentals, compares asynchronous and synchronous modes, walks through configuring a master‑slave environment with binary logs, details statement‑based and row‑based replication, offers recommended settings, and discusses replication lag, semi‑synchronous replication, and heartbeat mechanisms.
This comprehensive guide explains MySQL's various log types, how to view and configure error, general, slow, and binary logs, and details essential server variables for effective database administration and troubleshooting.
This tutorial walks through three MySQL backup and recovery strategies—using mysqldump with binary logs, LVM snapshots with binary logs, and Percona Xtrabackup—detailing environment setup, command syntax, incremental procedures, and restoration steps to ensure data safety and minimal downtime.
