The article presents a comprehensive overview of the Home (ZhiJia) distributed task scheduling system, detailing its background, advantages, technology stack, architecture, core concepts, module responsibilities, IDE integration, and future improvement plans for big‑data processing workflows.
This guide explains the fundamentals of MySQL master‑slave replication, the advantages of using GTID‑based replication, and provides detailed configuration steps, command examples, and troubleshooting tips for setting up and managing a reliable, read‑scalable database environment.
This article provides a comprehensive overview of Jenkins' architecture, detailing the master and slave nodes, web interface, jobs, plugins, security, credentials, cloud agents, global settings, logging, configuration storage, connection methods, and best practices for backup and deployment.
This guide details a step‑by‑step process for creating, debugging, and scaling JMeter scripts, performing sandbox tests on BlazeMeter, configuring engine user limits, building clusters, and using master‑slave mode to achieve a 50 k concurrent‑user load test.
This article explains the principles of MySQL master‑slave replication and provides a detailed, step‑by‑step tutorial for configuring a master and a slave instance in a Docker environment, including configuration files, Docker commands, replication setup, testing, and troubleshooting.
This article provides a comprehensive MySQL replication FAQ covering cross‑OS and hardware compatibility, master‑slave connection behavior, monitoring lag, forcing master pause, bidirectional replication considerations, performance improvements, high‑availability setups, and how to exclude GRANT/REVOKE statements from replication.
This article explains OpenStack Trove’s role as a Database-as-a-Service platform, outlines its core components, and details QiYun’s custom enhancements—including automated backup, monitoring, and a streamlined single-API master-slave instance creation with isolated networks and VIP-based failover for improved security and availability.
The article explains that although Kafka could technically implement a master‑slave (write‑read) model, it deliberately avoids it because the master‑write master‑read design already provides superior load balancing, consistency, and lower latency, making a separate read‑only replica unnecessary.
This article explains why MySQL master‑slave replication lag occurs, why it matters for data consistency and high‑availability, and provides six real‑world case studies with root‑cause analysis and practical solutions to eliminate the delay.
This guide walks you through the complete process of planning, scripting, locally testing, and scaling a load test to over 50,000 concurrent users using JMeter and BlazeMeter, covering script creation, sandbox configuration, engine sizing, cluster setup, and master‑slave orchestration.
The article explains Kafka’s master‑write master‑read architecture, why it does not implement a master‑write slave‑read model, the trade‑offs of consistency and latency, and how Kafka achieves load balancing through its leader‑replica design and operational safeguards.
This article examines the common causes of MySQL master‑slave replication delay, explains how to monitor the issue with SHOW SLAVE STATUS, and provides practical solutions for six typical scenarios ranging from heavy write traffic to hardware mismatches.
The article recounts a pre‑promotion MySQL replication incident at JD.com, explains the master‑slave architecture and thread roles, identifies slow‑SQL and missing indexes as root causes of replication lag, and proposes practical measures to reduce latency and improve system stability.
This guide explains why a single MySQL server is a bottleneck, how to form a clustered master‑slave architecture, the binlog and GTID replication mechanisms, step‑by‑step configuration commands, and the trade‑offs of each approach.
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 how to implement a one‑master‑multiple‑backup high‑availability scheme using a database table for instance registration, automatic leader selection, heartbeat monitoring, and failover handling, with concrete examples and SQL snippets.
This guide walks through configuring MySQL master‑slave replication inside Docker containers, covering environment setup, container creation, MySQL configuration changes, replication user creation, synchronization commands, troubleshooting tips, and verification of data replication between the master and slave instances.
This article explains MyCat's role as a database middleware, tracing the evolution from single‑database setups through distributed deployment, caching, master‑slave, vertical and horizontal sharding, and shows how MyCat automates data‑source and shard selection to reduce code complexity.
This article walks readers through setting up MySQL replication, from the basic master‑slave model to a one‑master‑multiple‑slave cluster, covering configuration files, essential parameters, verification commands, performance tips, and common pitfalls for production deployments.
This tutorial explains how to set up two MySQL servers—one as master for writes and one as slave for reads—by configuring replication accounts, binary logging, server IDs, firewall rules, and then demonstrates read/write separation using a lightweight PHP framework.
The article uses everyday observations from a McDonald’s restaurant to illustrate core distributed system concepts such as master‑slave architecture, two‑phase commit, microservice decomposition, task queues, and container orchestration, showing how these principles apply to backend engineering.
This guide walks you through building custom MySQL Docker images, configuring master and slave my.cnf files, launching the containers, creating a replication user, and synchronizing the slave using Docker commands and a ready‑made shell script, all with detailed code examples.
This article explains how MySQL 5.7 master‑slave replication works, covering the binlog formats, replication threads, event types, common causes of replication lag, and practical strategies to reduce latency and improve database availability.
This article provides a comprehensive, step‑by‑step tutorial on setting up MySQL master‑slave replication, covering basic principles, configuration of master and slave servers, recommended hardware, scaling to multiple slaves, and the key limitations of the architecture.
This article explains Pika's master‑slave replication architecture, detailing its specialized threads, full and incremental replication workflows, key API functions, and the slaveof and trysync processes that enable persistent, large‑scale data synchronization beyond Redis limitations.
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 the concept of read/write splitting in distributed databases, outlines two implementation methods—static dual data sources and dynamic AOP-based switching—provides a complete Spring‑MyBatis demo with configuration files, code snippets, and guidance on setting up master and slave connections.
This guide explains what MySQL GTID is, compares its advantages and disadvantages to traditional binlog‑position replication, and provides a detailed, step‑by‑step procedure for configuring GTID‑based master‑slave replication, including server‑UUID handling, configuration files, data export, user creation, and verification.
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.
An experienced Tencent Cloud engineer shares a detailed case study of moving over 130 MySQL instances (20 TB) from on‑premise IDC to CDB for MySQL, covering test cases, migration tool mechanics, multi‑instance concurrency, binlog handling, encountered issues, and practical solutions that ensured a smooth, high‑availability transition.
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.
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.
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 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.
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 analyzes the use of a master/slave architecture for distributed caching, explains why two clusters, CAS, and proxy are employed, discusses consistency and availability challenges, and evaluates possible mitigation strategies for cache failures.
This article explains Redis replication's two core mechanisms—synchronization and command propagation—detailing the SYNC workflow, how masters propagate writes to slaves, and how the PSYNC command enables efficient partial resynchronization after disconnections.
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.
The article explains why Zookeeper is a crucial component for implementing master‑slave high‑availability architectures in distributed systems, detailing how temporary nodes, sequence numbers, and cluster coordination eliminate single points of failure and enable reliable failover for write services.
