This article explores RAID and replication strategies in distributed storage, detailing stripe concepts, RAID0/1/10/5/6 configurations, the typical three‑node architecture with metadata and data servers, performance bottlenecks, reconstruction experiments, and practical mitigation techniques to ensure data integrity and high availability.
This guide explains why data delay hurts MySQL replication, how MySQL 5.7’s logical‑clock multi‑threading improves throughput, and provides a detailed, command‑line walkthrough to configure, start, and verify multi‑threaded replication on a slave server.
This guide explains MySQL replication topologies—including one‑master‑one‑slave, one‑master‑multiple‑slaves, dual‑master, cascading, and dual‑master cascading—highlighting their benefits, load‑balancing strategies, and how to choose the right structure to minimize data latency.
This article critically examines Uber’s claim that MySQL outperforms PostgreSQL by dissecting the alleged PostgreSQL limitations, presenting detailed performance tests, and clarifying the true costs of write amplification, replication, and upgrade processes for both databases.
This article compiles a series of lesser‑known MySQL details—from case‑insensitive column names and fuzzy LIKE patterns to REPLACE INTO, INSERT … ON DUPLICATE KEY UPDATE, EXPLAIN usage, index length limits, replication methods, partitioning, slow‑query monitoring, binlog importance, advanced objects like views and stored procedures, and recommended client tools—helping developers avoid common pitfalls and write more efficient queries.
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 guide explains how to set up MySQL master‑slave replication, configure binlog, create users, synchronize data, troubleshoot common issues, and apply query‑performance optimizations such as limiting result sets, using covering indexes, and refactoring complex joins.
MySQL 5.7 introduces major enhancements such as native JSON support, an expanded Performance Schema, a new SYS Schema for health monitoring, improved security, advanced GIS capabilities, three‑fold query throughput gains, InnoDB optimizations, multi‑source replication, and a smarter optimizer with dynamic costing.
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.
Redis replication offers high‑availability through master‑slave syncing, supporting multiple slaves, cascading replication, non‑blocking data transfer, read‑write separation, and optional disk‑less sync, with detailed steps for configuration, safety considerations, partial resynchronization, and practical deployment examples.
This guide explains why MySQL replication can fail with errors 1452, 1032, and 1062, analyzes each root cause, and provides both quick‑fix procedures and a permanent solution using pt‑table‑checksum and pt‑table‑sync to keep master‑slave data consistent.
Learn how to diagnose MySQL master‑slave data drift using Percona Toolkit’s pt‑table‑checksum, configure necessary replication parameters, and automatically reconcile differences with pt‑table‑sync, including installation steps, command syntax, required privileges, and troubleshooting common errors for reliable database consistency.
After switching a MySQL master’s IP, the author observed extreme master‑to‑slave traffic and investigated whether using CHANGE MASTER with auto_position=1 forces the replica to re‑fetch already executed binlogs, especially when the replica is lagging.
This article reviews the main MySQL high‑availability architectures—including shared‑storage SAN, DRBD disk replication, keepalived/heartbeat, MHA, ZooKeeper‑based HA, Galera/PXC clustering, and middleware proxy solutions—detailing their principles, advantages, limitations, and suitability for different business scenarios.
The article analyzes distributed storage replication methods, explains how large‑scale replica recovery can trigger an avalanche effect, and proposes operational safeguards such as cross‑rack replica selection, flow‑control mechanisms, predictive fault handling, and a safety mode to maintain system stability.
This guide compares Percona Server, MariaDB, and MySQL, outlines practical MySQL performance tuning steps across hardware, storage, filesystem, and server parameters, and presents several high‑availability architectures such as master‑slave replication, MMM/MHA, Heartbeat/SAN, and Heartbeat/DRBD with real‑world deployment examples.
This article highlights thirteen often‑overlooked MySQL details—including case‑insensitive column names, LIKE pattern rules, REPLACE and INSERT ON DUPLICATE KEY syntax, EXPLAIN usage, index limits, replication methods, partitioning, slow‑query logging, binlog, advanced objects, and useful client tools.
The article explains MySQL’s user authentication flow, detailing how the server loads and sorts the user table by host and user specificity, and walks through a real‑world replication user login issue that reveals a hidden empty‑user entry causing access denial.
This article analyzes why redirecting MySQLdump output can crash the client, explores a GTID_PURGED bug that breaks AUTO_POSITION replication, examines GTID gaps caused by replicate‑do‑db filtering, and explains why TokuDB's OPTIMIZE TABLE appears to increase table size.
This article presents a series of MySQL backend improvements—including Group Commit redesign, DDL fast‑fail handling, GTID allocation refinements, persistent InnoDB auto‑increment values, replication parallelism, and key‑partition hash algorithm changes—detailing motivations, implementation steps, and performance results.
A MySQL replica was consuming an entire CPU core due to single‑process replication, and analysis of binlog and InnoDB status revealed heavy row locks on a table without a primary key, which was resolved by adding an auto‑increment ID, dropping CPU usage to 3% and eliminating replication lag.
This guide walks through adding a third MySQL replica to an existing master‑slave setup without restarting the service, comparing a logical mysqldump backup method with the faster physical XtraBackup approach and providing step‑by‑step commands and configuration details.
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 article examines the various scenarios in which MySQL can lose data, covering InnoDB and MyISAM engine behaviors, flush policies, master‑slave replication pitfalls, XA transaction handling, and practical solutions to improve consistency and availability.
This article explains the fundamentals of distributed file systems, focusing on Hadoop’s HDFS architecture, the separation of metadata and data via NameNode and DataNode, and detailed step‑by‑step write and read processes, including replication, fault recovery, and block splitting across nodes.
The article explains how MySQL replication parameters such as expire_logs_days, relay-log-recovery, and relay-log-info-repository affect binlog cleanup, SQL and I/O thread consistency, and why crashes can produce duplicate‑key errors, then offers configuration fixes including the critical relay‑log cleaning option and the super_read_only setting.
This article explores practical MySQL high‑availability solutions, covering asynchronous and semi‑synchronous replication, monitoring with keepalived or Zookeeper, failover decision criteria, GTID and pseudo‑GTID techniques, and lessons learned from real‑world deployments.
This article provides a comprehensive technical overview of Apache Kafka, covering its architecture, core concepts, design goals, comparison with other message queues, replication, consumer groups, delivery guarantees, and performance benchmarking, making it a valuable resource for big‑data engineers.
Kafka introduced a high‑availability mechanism in version 0.8 by replicating partitions across multiple brokers, designating a leader and followers, using an in‑sync replica (ISR) list to balance synchronous and asynchronous replication, and employing leader election strategies to maintain data integrity during failures.
The article analyzes the architecture of TDSQL, a MySQL‑based distributed SQL system designed for Tencent’s billing platform, detailing its transition from an in‑memory NoSQL solution to a high‑consistency, auto‑scaling, fault‑tolerant database with sharding, scheduler, agent, and gateway components.
This article explains how MySQL 5.6 introduced parallel replication to overcome the bottleneck of a single SQL thread, detailing the underlying binlog events, configuration parameters, key data structures, worker coordination, checkpoint mechanisms, and potential limitations, all from a source‑code perspective.
This article explains how Booking.com solved MySQL master‑to‑hundreds‑of‑slaves bandwidth limits by introducing a Binlog Server component, detailing its design, advantages over traditional relay‑master setups, and multiple deployment scenarios for high‑availability and cross‑region replication.
This article explains why Kafka introduced high‑availability features after version 0.8, detailing the necessity of data replication and leader election, describing Kafka’s replica distribution algorithm, replication mechanics, acknowledgment requirements, leader‑election strategies, Zookeeper structures, and the broker failover process.
The article presents the Binlog Server, a component that replaces intermediate masters in MySQL replication topologies to reduce network saturation, simplify disaster recovery, and improve high‑availability while supporting large numbers of slaves across remote sites.
Understanding MySQL master‑slave replication hinges on optimizing binlog size; by configuring master parameters like Binlog_Do_DB and Binlog_Ignore_DB and slave filters such as Replicate_Do_DB, Replicate_Ignore_DB, Replicate_Do_Table, and wildcard options, you can reduce I/O, network load, and replication errors.
This article provides a comprehensive overview of Redis, covering its primary use cases, internal network and memory models, data consistency, supported data types, client libraries, replication mechanisms, read‑write separation, eviction policies, cluster architecture, node communication, redirection handling, online reconfiguration, and fault‑tolerance strategies.
The article reviews MongoDB's storage engine developments—including MMAP, WiredTiger, RocksDB, and Memory engines—highlights replication protocol improvements, automatic sharding changes, and introduces new features such as batch and partial indexes, document validation, and join capabilities, while providing performance test results and a Q&A section.
This article presents a comprehensive guide to MySQL optimization, covering its strengths and weaknesses, daily DBA tasks, development and operational standards, sharding strategies, backup solutions, performance tuning, replication options, InnoDB configuration, system-level tweaks, and future improvement directions.
This guide outlines a structured MySQL DBA interview process, covering self‑introduction, resume deep‑dive, career‑development questions, fundamental knowledge such as index types, core technical skills like backup, replication and performance troubleshooting, and broader potential areas including Linux and programming language proficiency.
This article explains MySQL replication fundamentals, detailing master‑slave and multi‑master architectures, thread roles, configuration parameters, read‑write splitting, multi‑source setups, and advanced scenarios such as multi‑level and circular replication, while highlighting common pitfalls and performance considerations.
This article compiles Russell Smith’s comprehensive MongoDB best‑practice guide, covering architecture choices, file limits, write safety, schema design, replication, sharding, security, and performance tuning to help engineers avoid common pitfalls and optimize production deployments.
This article explains how Redis master‑slave replication works, covering asynchronous copying, partial resynchronization, disk‑less replication, safety considerations when persistence is disabled, read‑only slaves, authentication, and configuration options such as slaveof and write‑restriction based on slave count.
The article examines two common MySQL master‑slave delay scenarios—slow ALTER operations and MyISAM table‑level locks—explains why they cause replication lag, and offers practical mitigation steps such as scheduling problematic SQL, isolating lagging slaves, and tuning binlog write settings.
The article explains Amazon’s Dynamo distributed key‑value store architecture, covering its decentralized design, consistent hashing with virtual nodes, replication strategies, quorum‑based read/write parameters, vector‑clock versioning, failure detection, hinted handoff, scaling mechanisms, and how these techniques together provide high availability, scalability, and reliability.
This article introduces NoSQL concepts, compares common storage models, and details MongoDB's replication architectures, special node roles, synchronization processes, and the variety of index types available for efficient data handling.
This article examines several MySQL issues—including key partition hash algorithm changes causing data loss after upgrades, a client crash triggered by misdirected dump output, GTID_PURGED interactions that break AUTO_POSITION replication, and replicate‑do‑db filtering effects on GTID continuity—and provides concrete compatibility fixes and troubleshooting steps.
This article provides a comprehensive guide to MySQL performance optimization, covering isolation levels, MVCC, schema design, index strategies, query execution, partitioning, replication, scaling, hardware considerations, and backup/recovery techniques for building high‑performance, reliable database systems.
This article examines why MySQL 5.5/5.6 fails to retrieve non‑null partitioned rows after a physical upgrade, how the ALTER TABLE … PARTITION BY KEY ALGORITHM=1 fix works, the cause of MySQL client crashes when dump output mixes warnings, GTID_PURGED replication bugs, replicate‑filter side effects, and the behavior of TokuDB’s OPTIMIZE TABLE.
This article explains MySQL's evolution from serialized binlog writes to group commit, introduces DDL fast‑fail and GTID allocation improvements, analyzes InnoDB auto‑increment duplication after restart, and details replication performance gains from multi‑threaded and seqno‑based parallel execution, providing code examples and benchmark results.
This article systematically explores the distributed characteristics of NoSQL databases, covering data consistency, placement, peer systems, anti‑entropy protocols, eventual consistency data types, sharding, fault detection, and coordinator election, illustrating how these strategies balance scalability, availability, latency, and fault tolerance.
This article explains why MySQL migrations are essential, outlines backup and restore strategies, and provides detailed, step‑by‑step procedures for multiple real‑world scenarios—including single‑master/slave moves, cross‑datacenter transfers, and multi‑instance setups—while highlighting key precautions and practical tips for successful execution.
This article explains why MySQL migration is essential, outlines various migration strategies—including full, partial, and cross‑datacenter moves—and provides detailed, step‑by‑step procedures, best‑practice tips, and precautionary measures to ensure a smooth, reliable transition.
This article reviews various MySQL high‑availability architectures—including master‑slave replication with keepalived or MHA, Galera‑based clusters, and other approaches—detailing their deployment methods, advantages, limitations, and practical considerations for selecting an appropriate HA solution.
DD Boost allows backup applications to manage and simplify file replication between multiple Data Domain systems, and using NetWorker as an example, the article details the step‑by‑step replication workflow, optional low‑bandwidth and encryption features, and how remote restores are performed.
This article discusses MySQL high‑availability solutions, covering asynchronous and semi‑synchronous replication, monitoring with keepalived, Zookeeper, and custom agents, failover procedures using binlog positions, GTID and pseudo‑GTID techniques, and the author's practical experiences and future plans.
This article outlines the four main types of MySQL physical files—system, log, replication, and data files—detailing their purposes and showing visual examples to help database administrators manage storage effectively and ensure optimal performance.
This article systematically explores the distributed characteristics of NoSQL databases, covering consistency trade‑offs, replication techniques, anti‑entropy protocols, data placement strategies, failure detection, and coordinator election, while illustrating each concept with diagrams and practical examples.
Redis uses both lazy and periodic deletion strategies to remove expired keys, balancing CPU usage and memory efficiency, and these strategies also affect how persistence mechanisms like RDB and AOF as well as master‑slave replication handle expired keys.
When read traffic overwhelms a single MySQL master, cascading replication and dual-master setups can distribute slave load, reduce replication lag, and simplify failover, offering a scalable solution that balances read/write pressure across multiple replication layers.
This article examines the problems and trade‑offs of metadata protection in cloud object storage, highlighting the importance of reliability, availability, and consistency, and comparing primary‑secondary and multi‑replica models, including the WRN algorithm and practical operational considerations.
An expert panel from the High‑Efficiency Operations community answers eleven pressing MySQL 5.7 questions, covering test hardware, GA timeline, GIS speed, virtual column indexing, materialized view plans, 2‑D geo support, performance monitoring, Oracle’s market strategy, geojson handling, multi‑source replication, buffer‑pool locking, and InnoDB Memcached consistency.
The article describes the evolution, architecture, automatic scaling, sharding, disaster‑recovery mechanisms, and strong synchronous replication strategy of TDSQL, a MySQL‑engine based distributed database built to meet the high‑availability and high‑consistency requirements of Tencent's billing platform.
This article presents 58.com’s experience with MySQL under massive data volumes, covering core concepts such as single‑instance, sharding, replication and grouping, common availability and read‑write challenges, detailed sharding implementations for user, post, friend and order tables, and post‑sharding business practices including IN queries, non‑partition key queries, and cross‑database pagination.
This article explains the fundamental reasons why MySQL slave servers experience higher latency than masters and provides practical optimization techniques—including parallel replication, proper indexing, I/O improvements, and hardware choices—to reduce replication lag.
This article explains a rare MySQL replication scenario where Seconds_Behind_Master stays at zero while the slave cannot receive updates, analyzes the underlying push‑based replication mechanism, and offers practical steps and configuration tweaks to detect and prevent the issue.
This article presents a comprehensive technical overview of MySQL performance tuning and feature enhancements—including group‑commit redesign, DDL fast‑fail, GTID handling, persistent auto‑increment, replication parallelism, and key‑partition hash changes—backed by real‑world test data from Taobao's large‑scale deployment.
This article highlights several often‑overlooked MongoDB limitations—including excessive disk‑space preallocation, a 12‑node replica‑set cap, lack of high‑availability in master‑slave mode, 32‑bit version constraints, high consulting fees, and weak management tools—helping developers avoid costly surprises.
