This article compiles ten classic MySQL error scenarios—from connection limits and replication conflicts to charset issues and file‑open limits—explaining the root causes, diagnostic commands, and step‑by‑step solutions so beginners and seasoned DBAs can troubleshoot confidently.
At HBaseCon 2017 Asia, Alibaba showcased a series of groundbreaking HBase enhancements—including strong synchronous replication, SQL-on-HBase capabilities, cross‑cluster range data copy, and read/write path optimizations—that dramatically improve performance, reliability, and usability for large‑scale big‑data storage.
This comprehensive guide introduces Redis fundamentals, explores its rich data structures and essential commands, delves into performance optimization techniques, explains replication and clustering strategies, and compares popular Java clients, providing practical examples and best‑practice recommendations for reliable, high‑performance deployments.
A senior MySQL engineer recounts a puzzling case where a custom script flushing relay logs caused the first transaction in each relay log to be skipped, leading to daily loss of nearly ten thousand rows in a rapidly growing production environment.
This article outlines a comprehensive Redis multi‑datacenter deployment plan, detailing master‑backup placement, tree‑structured master‑slave topology across three sites, configuration checks, Pull&Push synchronization mechanics, and includes concrete code snippets illustrating connection, RDB generation, and incremental replication processes.
PacificA is Microsoft’s generic replication framework for large‑scale distributed storage systems that provides strong consistency, separates configuration management from data replication, and uses a primary‑secondary model with lease‑based fault detection to ensure availability, correctness, and efficient operation across heterogeneous nodes.
Distributed file systems extend traditional local storage by partitioning data across multiple servers, using a master node for metadata and coordination, handling namespace, replication, load balancing, caching, and client interfaces, thereby overcoming file size, quantity, and concurrency constraints of ext3, reiserfs, and similar local filesystems.
During synchronization from MySQL 5.0 to 5.7, a slave worker raised a ‘duplicate primary’ error; the article examines binlog statements, auto‑increment values, and a problematic trigger, walks through various debugging attempts, and concludes that removing the trigger resolves the issue despite unclear root cause.
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.
This article explains Kafka's distributed architecture, topic‑partition model, replication and ISR mechanisms, data durability settings, delivery guarantees, deduplication strategies, and presents benchmark results that illustrate how configuration choices affect throughput and latency in real‑world deployments.
This article provides an in‑depth technical analysis of Amazon Aurora’s cloud‑native relational database design, covering its architectural models, log‑as‑database philosophy, optimized write and read paths, fault‑tolerant replication, group commit, and fast recovery mechanisms compared with traditional DBMS.
The article explains high‑availability concepts, compares typical MySQL HA architectures—including replication, clustering, and Paxos‑based solutions—and presents UDB’s dual‑master semi‑synchronous design with a Proxy layer that ensures automatic failover, data consistency, and operational resilience.
This article explains how distributed file systems overcome the limitations of traditional local file systems by using a master‑metadata server, multiple data nodes, and client interfaces, and it details the key architectural components, common problems, and practical engineering solutions such as replication, load balancing, and caching.
This article reviews core database high‑availability technologies—including IBM DB2 HADR, HACMP clustering, SQL and Q replication, storage‑level disaster recovery, and DPF considerations—explaining their mechanisms, suitable scenarios, and practical deployment tips for enterprise environments.
This article introduces XPipe, a framework designed by Ctrip to enable Redis multi‑data‑center replication, ensure high availability through keeper and MetaServer components, and provide reliable disaster‑recovery (DR) switching while maintaining low latency and data consistency.
This guide walks through preparing three CentOS 6.7 machines, installing MySQL 5.7.17, configuring my.cnf, disabling firewalls and SELinux, creating replication users, exporting databases, setting up multi‑source replication with GTID, and verifying data consistency across two masters and one slave.
The article explains how achieving high availability through data redundancy introduces consistency challenges that in turn affect performance, and it reviews partitioning, mirroring, consistency models, replication architectures, and two/three‑phase commit protocols in distributed systems.
This article explains why a large‑transaction update caused a binlog overflow and slave I/O failure in a remote MySQL master‑slave setup, and provides step‑by‑step commands and a stored‑procedure solution to restore replication safely.
This article details how Alibaba has evolved HBase from an internal storage solution to a cloud service, covering its architecture, high‑availability design, asynchronous and synchronous replication, multi‑link data flows, cost‑effective redundancy, performance optimizations, and future development directions.
This article describes Alibaba's extensive use of HBase, covering its architecture, high‑availability replication strategies, multi‑link data flow, synchronous and asynchronous replication, performance optimizations, data export pipelines, and future development plans for the distributed NoSQL database.
This article explains how Alibaba built, customized, and operated a massive HBase platform—covering its architecture, high‑availability design, asynchronous and synchronous replication, multi‑link data flow, cost‑aware redundancy, cross‑cluster migration, performance optimizations, and future directions for the distributed NoSQL database.
This article walks through a real‑world MySQL 5.7 memory‑leak case, showing how to use performance_schema, pmap, and thread analysis to identify runaway threads and fix the issue by closing unclosed cursors.
This article outlines the five evolutionary stages of a MySQL deployment—table design, deployment, performance tuning, architecture scaling, and maintenance—detailing practical configuration tweaks, kernel and hardware optimizations, replication strategies, caching, sharding, partitioning, and essential monitoring and backup techniques.
This curated excerpt from the MySQL 5.7 FAQ provides concise answers on NDB Cluster versions and deployment, network and hardware requirements, memory sizing formulas, virtual machine support, common error causes, user management, replication setup and limitations, trigger behavior, and InnoDB tablespace encryption details, linking to official documentation for deeper reference.
This article offers comprehensive advice on MySQL DBA interview preparation, covering the book’s positioning, essential technical topics such as replication and InnoDB internals, desired personal qualities, interview strategies, and practical tips for both interviewers and candidates.
In this interview, veteran database director Zhou Yanwei shares his ten‑year MySQL journey, the founding of the China MySQL User Group, his views on why MySQL thrives, the essential DBA spirit, learning strategies, and predictions for MySQL’s future in enterprise environments.
This article provides a comprehensive, step-by-step tutorial for downloading, installing, and configuring three MySQL 5.7.17 instances on a single server, creating users, setting up Group Replication, adding members, and verifying data synchronization across the replication group.
Oracle TimesTen In-Memory Database, acquired by Oracle, offers a memory-optimized relational database with shared libraries, checkpointing, logging, and advanced replication options such as synchronous and asynchronous data replication, cache integration, and broad OS/CPU compatibility, positioning it as a high‑performance alternative to traditional RDBMS.
This article explains Redis fundamentals, its key‑value storage model, advanced data structures, persistence mechanisms (RDB and AOF), replication architecture, and how Sentinel provides automated failover and high‑availability management, complemented by practical configuration examples and performance considerations.
This article explains MySQL's asynchronous, semi‑synchronous, and Group Replication mechanisms, compares their trade‑offs, details Group Replication’s certification‑based full‑sync workflow, lists its features and limitations, and provides a complete configuration and maintenance guide for a three‑node cluster.
This article explains why MySQL master‑slave replication is essential for high availability, describes the replication mechanism, provides detailed configuration commands for both master and slave servers, and shows how to test and recover synchronization when inconsistencies occur.
This article explains how MariaDB, a community‑driven fork of MySQL, maintains full compatibility while adding new storage engines, advanced replication, performance‑boosting features like XtraDB and thread pools, and why many organizations consider it a superior replacement for Oracle‑owned MySQL.
This comprehensive guide explains MySQL GTID fundamentals, its syntax, how to view and generate GTIDs, configure GTID‑based replication, troubleshoot replication errors, integrate GTID with backup/restore, MHA failover, and ensure crash‑safe slaves while discussing performance trade‑offs.
This guide explains how to use the Perl‑based MMM tool to monitor and manage MySQL master‑master replication, covering its advantages, working principle, detailed server configurations, connection steps, master‑slave testing, and high‑availability failover demonstrations.
This article provides a comprehensive, hands‑on guide to MySQL master‑slave replication, covering configuration changes, creating replication users, backing up the master, restoring to slaves, setting up read/write splitting, handling master failures, implementing dual‑master setups, and performing full and incremental backups and restores.
This guide walks through the reasons for sharding in MongoDB, explains the sharding architecture, and provides detailed commands to configure config servers, shard servers, and mongos, add shards, enable sharding on databases and collections, insert test data, and verify successful data distribution across shards.
This guide walks through extending MySQL 5.6.32 by adding a new SQLCOM_STOP_SLAVES command that stops all replication slaves, detailing modifications to lex.h, sql_cmd.h, sql_yacc.yy, sql_parse.cc, and mysqld.cc, along with compilation tips and troubleshooting steps.
This article explains MySQL replication fundamentals, explores multi‑source master‑slave architectures, details step‑by‑step configuration for both basic 1‑master‑1‑slave and multi‑source setups, introduces parallel replication to boost performance, and presents Sysbench‑based testing results that demonstrate the efficiency gains.
This comprehensive guide presents the most common MongoDB interview questions, covering NoSQL fundamentals, replication, sharding, transactions, profiling, storage nuances, and operational details, providing concise yet thorough answers to help candidates confidently tackle technical interviews.
This guide explains MySQL's Multi‑Source Replication feature, its use cases, and provides a detailed GTID‑based configuration process—including master and slave setup, unique server IDs, replication user creation, and verification of successful replication across multiple masters.
This article explains core database concepts such as sharding, replication, routing strategies, and high‑availability designs, detailing how to achieve read/write separation, cache integration, and consistency handling in a master‑slave architecture for large‑scale systems.
This article explains NetEase Hive RDS's instance migration feature, covering use cases, technical challenges such as consistent backup, business impact, data import speed, incremental sync, and the solutions implemented—including multi‑threaded logical backup with mydumper, load‑aware throttling, parallel import with myloader, and filtered replication—to achieve efficient and safe MySQL migrations.
This guide explains how MySQL's asynchronous replication works, shows how to configure a master‑slave setup in seconds using the mysqlreplicate command from MySQL Utilities, and introduces additional utility commands for disk usage and index checking.
This article explains Redis’s master‑slave replication mechanism, compares the full‑copy process of Redis 2.4.16 with the partial‑copy improvements introduced in Redis 2.8, details the state machine, replication‑cron workflow, repl_backlog buffer, run‑id handling, and configuration options for optimizing partial synchronization during network interruptions.
This article explains Oracle Data Guard's three protection modes—Maximum Performance, Maximum Availability, and Maximum Protection—detailing their underlying redo‑log mechanisms, configuration steps, and test results that illustrate how each mode behaves under various failure scenarios.
This guide walks you through configuring a MySQL master‑slave cluster on two Linux servers, covering MySQL configuration files, service restarts, replication user creation, master status capture, slave setup, start‑up, verification, testing data sync, and troubleshooting common issues.
This article outlines the lifecycle of a mature MySQL database architecture, covering table design, deployment, performance tuning, scaling strategies such as replication, sharding and partitioning, as well as maintenance tasks like monitoring, backup, and repair, with practical configuration examples.
The article explains how MySQL’s ease of use, open‑source nature, early replication support, flexible storage‑engine architecture, and strong community contributions have driven its widespread adoption and sustained popularity in modern high‑concurrency, high‑availability applications.
This tutorial shows how to create a three‑node MongoDB replica set using Docker, configure automatic primary election, verify data synchronization across secondaries, and simulate a primary failure to observe failover, providing a practical guide for high‑availability database deployments.
This guide explains how to back up a MySQL Galera Cluster by leveraging the State Snapshot Transfer (SST) mechanism, detailing the default and custom scripts, required parameters, execution flow, and the key benefits of using SST for point‑in‑time, non‑intrusive backups.
PhxSQL is an open‑source, MySQL‑compatible relational database cluster that uses a Paxos‑based log store and a three‑layer architecture (Phxbinlogsvr, Phxsqlproxy, Phxsync) to provide automatic master failover, strong data consistency, and improved write performance compared to MySQL semi‑synchronous replication.
This article provides a detailed guide on installing Redis on Linux, configuring protected mode, using Java's Jedis client with Maven, performing message‑queue performance tests, comparing RDB and AOF persistence, and explaining master‑slave replication with configuration tips and code examples.
This article examines common MySQL high‑availability designs—including single master‑slave, dual‑master with multiple slaves, Heartbeat + DRBD, MySQL Cluster, semi‑synchronous replication, and GTID—explaining their benefits, drawbacks, and practical considerations for reliable failover and scalability.
This guide introduces MySQL Utilities, demonstrates how to configure master‑slave replication in seconds using the mysqlreplicate command, explains required user creation, showcases additional tools like mysqldiskusage and mysqlindexcheck, and provides installation and download instructions.
This comprehensive Redis guide explains the in‑memory key‑value store’s installation, basic commands, configuration options, supported data structures, persistence mechanisms, replication, transactions, pub/sub, performance testing, connection handling, pipelining, and partitioning, providing practical examples for developers.
This article demonstrates how MaxScale manages MySQL read/write splitting when one or both slave servers fail, showing log configurations, state changes, and how to configure a stable master to maintain service continuity even when all slaves are down.
This article analyzes two deadlock cases that occur when running Percona‑XtraBackup on a MySQL 5.6 replica, explains the underlying lock interactions, shows how to reproduce the issue with SystemTap, and provides safe remediation steps for operators.
The article explains how Redis replicas can return keys that should have expired due to the master‑only expiration process, describes the three expiration strategies (lazy, periodic, active), and offers practical solutions such as using SCAN or upgrading to Redis 3.2 to avoid stale reads.
MHA (Master High Availability) ensures MySQL cluster resilience by monitoring the master, automatically promoting the most up‑to‑date slave as a new master during failures, offering fast failover, strong data safety, easy extensibility, and multi‑cluster management, while noting its limitations.
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.
