BestHub
Sign in
Tag

Database HA

0 views collected around this technical thread.

Aikesheng Open Source Community
Aikesheng Open Source Community
Nov 7, 2022 · Databases

Orchestrator Failover Process Source Code Analysis – Simulating Faults and Understanding ContinuousDiscovery

This article walks through a simulated MySQL 3307 cluster failure, examines Orchestrator's source code to explain the ContinuousDiscovery loop, discovery queues, health ticks, caretaking tasks, raft coordination, topology snapshots, and the logic distinguishing UnreachableMaster from DeadMaster states.

ContinuousDiscoveryDatabase HAFailover
0 likes · 20 min read
Orchestrator Failover Process Source Code Analysis – Simulating Faults and Understanding ContinuousDiscovery
Aikesheng Open Source Community
Aikesheng Open Source Community
Dec 22, 2021 · Databases

Configuring ProxySQL with MySQL Replication and Group Replication for Read/Write Splitting and Automatic Failover

This guide demonstrates how to deploy a ProxySQL instance alongside six MySQL servers (three for traditional replication and three for MySQL Group Replication), configure users, set up read/write splitting rules, and enable automatic failover for both replication topologies.

Database HAFailoverGroup Replication
0 likes · 14 min read
Configuring ProxySQL with MySQL Replication and Group Replication for Read/Write Splitting and Automatic Failover
Aikesheng Open Source Community
Aikesheng Open Source Community
Mar 20, 2019 · Databases

Analysis of MySQL Group Replication Data Inconsistency Caused by GTID Mismatch and Paxos Proposal Conflict

This article examines a real‑world MySQL Group Replication failure where network jitter caused a primary INSERT not to replicate, leading to GTID divergence, a secondary node leaving the cluster, and explains the underlying Paxos‑based proposal conflict with detailed code examples.

Data InconsistencyDatabase HAGTID
0 likes · 11 min read
Analysis of MySQL Group Replication Data Inconsistency Caused by GTID Mismatch and Paxos Proposal Conflict
Ctrip Technology
Ctrip Technology
Nov 8, 2018 · Databases

Evolution of Ctrip's Database High‑Availability and Disaster‑Recovery Architecture (1999‑2018)

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.

AlwaysOnDatabase HAMHA
0 likes · 10 min read
Evolution of Ctrip's Database High‑Availability and Disaster‑Recovery Architecture (1999‑2018)