1 views collected around this technical thread.
This article explains how Nginx's master‑slave (primary‑backup) setup, combined with Keepalived and a virtual IP, provides high‑availability for web and API services by automatically detecting failures, shifting the VIP, and allowing the backup server to take over without service interruption.
Redis cluster relies on two ports per node, a hash‑slot based sharding scheme, a master‑slave replication model, and provides eventual consistency, making these four fundamentals essential knowledge for developers and operators to.
This tutorial walks through preparing the Linux environment, installing MySQL 5.7, configuring master and slave servers, creating replication users, verifying synchronization, troubleshooting common issues, and applying advanced options such as GTID and semi‑synchronous replication, all with complete command examples.
This article explains how RocketMQ achieves high availability and data reliability through its master‑slave broker design, covering synchronous and asynchronous replication, flush strategies, transaction messaging, automatic failover with Dledger, and read‑write separation for load balancing in distributed systems.
This tutorial explains how to use SpringBoot, AOP, and a custom @DataSource annotation to dynamically switch between MySQL master and slave databases—covering configuration, code implementation, multiple slave handling, and an Oracle example—to ensure high availability and flexible data source management.
This guide walks you through preparing multiple virtual machines, configuring MySQL server IDs, setting up both classic and GTID‑based master‑slave replication, and managing the replication with essential commands, complete with code examples and architecture diagrams.
This article explains Redis split‑brain behavior, describing its definition, causes such as network failures and Sentinel elections, the resulting data loss during master‑slave switches, and practical prevention measures including quorum configuration, timeout tuning, network monitoring, proxy layers, and the min‑slaves‑to‑write and min‑slaves‑max‑lag settings.
This article reviews the four common Redis deployment modes—single‑instance, master‑slave replication, Sentinel, and cluster—explaining their architectures, advantages, drawbacks, and suitable application scenarios, and provides a comparative table to help readers choose the appropriate setup.
The article compares master‑slave, master‑master, and leaderless distributed architectures, explaining how synchronous, semi‑synchronous, and asynchronous replication affect consistency, latency and scalability, and showing that each pattern trades write throughput, conflict‑resolution complexity, and availability against strong data correctness.
This article explains why read‑write separation is essential for high‑concurrency systems and details three MySQL master‑slave synchronization methods—half‑synchronous replication, database‑middleware synchronization, and cache‑key write tracking—along with their advantages, drawbacks, and consistency considerations.
This article explains MySQL's binary log (binlog), a binary format file that records SQL statements for database updates, its role in master-slave replication, crash recovery, and detailed implementation mechanisms including cache management and event writing processes.
This guide walks through preparing two servers, installing Jenkins on a master node, configuring security and communication, adding a slave node with detailed parameters, deploying the slave agent as a Windows service, creating a slave-bound project, and troubleshooting common issues such as permission errors and network mismatches.
This article examines the evolution of database high‑availability architectures in large‑scale internet environments, covering basic direct‑connect setups, scale‑up/scale‑out sharding, master‑slave/master‑master with Keepalived, and advanced solutions such as MHA, Percona XtraDB Cluster, and MySQL Group Replication, plus smooth scaling steps.
This article explains MySQL master‑slave replication, covering its architecture, binlog‑based replication process, causes and mitigation of replication lag, and strategies for master‑slave failover, helping readers grasp why and how to use replication for read/write separation, high availability, and backup.
This article explains Jenkins’ distributed master‑slave architecture, the requirement for identical slave environments, outlines the roles of master and slaves, and provides step‑by‑step solutions for common node errors such as SSH connection failures and JDK version mismatches.
The article explains Redis master‑slave asynchronous replication, describes how repeated full‑sync requests from slaves can cause a replication storm that overloads CPU, memory and network, and offers practical solutions such as limiting data size, adjusting buffer limits, and redesigning deployment topology.
This article explains MySQL master‑slave replication, covering its basic concepts, the advantages of read‑write separation, data backup and high availability, the underlying binlog‑based mechanism, the four replication modes (full, asynchronous, semi‑synchronous, enhanced semi‑synchronous), common consistency challenges, and practical ways to mitigate them.
The article demonstrates via example how REPLACE INTO can cause data inconsistency and auto‑increment anomalies in master‑slave MySQL setups, explains the underlying binlog behavior, highlights risk points, and advises against using REPLACE when business logic depends on auto‑increment IDs.
The e‑commerce platform’s order‑query alerts were caused by MySQL master‑slave replication lag—specifically, delayed redo‑log flushing let the slave receive binlog events before the master committed—so queries returned empty, a condition mitigated by retry logic, delayed MQ delivery, or emitting post‑commit business events.
This article explains the CAP theorem, details how Redis implements master‑slave replication—including its asynchronous nature, configuration methods, three‑phase workflow, heartbeat mechanism, and common operational issues—providing practical guidance for building highly available Redis deployments.