0 views collected around this technical thread.
The article analyzes why a sed command freezes while modifying a MySQL MHA installation script on a CentOS 6 system, identifies the charset conversion issue caused by GBK locale and missing spaces after comment symbols, and provides a step‑by‑step debugging and fix procedure.
This article explains MySQL high‑availability concepts, defines HA, RPO and RTO, outlines common HA architectures such as master‑slave+VIP, MHA and MGR+Proxy, and details AutoHome's evolution from simple master‑slave setups to a container‑based MGR solution with automated failover and monitoring platforms.
The article explains why MHA’s default long‑connection ping cannot detect a hung MySQL instance, introduces three configurable ping_type options (select, connect, insert), shows how to modify the configuration and test the behavior with Perl code and shell scripts, and details the internal health‑check workflow.
This guide walks through the step‑by‑step deployment of MHA on a MySQL cluster, covering package installation on all nodes, copying and installing the MHA RPMs, creating the required MySQL user, configuring MHA, testing SSH connectivity, and reviewing the failover script.
The article explains how MHA handles a crashed MySQL master by preserving binary logs, selecting the most up‑to‑date slave, applying relay logs, promoting a slave to master, and provides detailed commands for creating replication users and configuring master‑slave replication.
This article analyses why MHA reports a "bad new master" error during master‑slave switches, explains the internal candidate‑master and bad‑master selection algorithms, demonstrates how MySQL version differences affect cross‑version promotion through test scenarios, and provides detailed code excerpts to illustrate the decision process.
This article examines the MHA open‑source MySQL high‑availability solution, detailing the master‑crash failover workflow, source‑code analysis, configuration checks, binlog handling, new‑master selection, and slave recovery, and provides a concise step‑by‑step checklist for practitioners.
This article explains the purpose, usage, and return codes of the MHA masterha_secondary_check Perl script, demonstrates how to simulate network failures with iptables, and presents a series of tests that verify the script’s ability to detect master reachability and handle various error conditions.
This article analyzes how adjusting the MHA ping_interval and enabling secondary_check_script can increase MySQL high‑availability cluster tolerance to network packet loss and corruption, presenting test setups, parameter configurations, log observations, and conclusions on their impact on failover behavior.
iQIYI’s custom MySQL HA solution replaces the single‑point‑failure MHA manager with a Raft‑based trio of HA Masters and HA Agents that continuously monitor instances, automatically perform same‑DC, cross‑DC, or cross‑region failovers, reconcile diff binlogs, ensure data consistency, and integrate with CMDB, tracing and chaos‑engineering platforms.
This article explains the need for high‑availability MySQL services, critiques the original in‑house HA approach, and details how the mature MHA framework was extended into WMHA with added VIP monitoring, enhanced failover procedures, richer notifications, and a reorganized deployment structure to improve reliability and reduce DBA intervention.
This article explains the importance of high availability in distributed systems, defines MySQL high‑availability concepts such as replication, describes several HA architectures including MySQL Cluster, MMM, and MHA, and discusses design principles for building resilient database services.
This article chronicles Ctrip's database high‑availability and disaster‑recovery evolution—from simple SQL Server mirroring in the early years, through SAN‑based clustering and AlwaysOn, to the adoption of MySQL, Redis, MHA, and a one‑click DR automation tool—highlighting architectural decisions, challenges, and operational lessons learned.
The article describes how a DBA team at Ele.me transformed manual database management into a fully automated, platform‑driven operation covering monitoring, alarm handling, MHA automation, resource pooling, large‑scale migration, SQL review, and multi‑active DDL release using Go‑based tools and custom workflows.
This article reviews the evolution of Meituan‑Dianping's MySQL high‑availability architecture over recent years, detailing the transition from the MMM replication manager to MHA, the integration of Zebra and Proxy middleware, and future design considerations such as distributed agents, semi‑synchronous replication, and MySQL Group Replication.
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.