mysql-replication-ha

Configure Percona Server for MySQL replication modes with 8.4 syntax.

1|1|Updated May 29, 2026
One-click install
npx skills add https://github.com/Percona-Lab/skills --skill mysql-replication-ha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mysql-replication-ha
Source: https://github.com/Percona-Lab/skills/tree/main/mysql-replication-ha
Command: npx skills add https://github.com/Percona-Lab/skills --skill mysql-replication-ha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage and optimize replication and high availability for Percona Server for MySQL, covering asynchronous replication, GTID-based workflows, semi-synchronous replication, and Group Replication, with version-aware guidance for 8.4 changes.

Core Features & Use Cases

  • Supports planning and implementing multiple replication modes (Async + GTID, Semi-Sync, Group Replication) and guidance on when to use each.
  • Provides configuration examples, monitoring tips for replica lag, GTID positioning, and failover scenarios.
  • Helps design scalable, resilient HA architectures and migrations between modes with 8.4 considerations.

Quick Start

Configure a replica using GTID-based replication and verify failover readiness in an 8.4 environment.

Frequently Asked Questions about mysql-replication-ha

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up GTID-based replication for Percona Server for MySQL?

GTID-based replication for Percona Server for MySQL requires configuring binlog behavior and GTID positioning on primary and replica nodes. This provides consistent transaction tracking and reliable failover readiness in 8.4 syntax environments.

When should I use semi-sync replication vs Group Replication in MySQL?

Choose semi-sync replication for reduced data loss risk with low latency, or Group Replication for automated multi-primary fault tolerance. Selecting between these modes depends on your HA architecture needs and distributed coordination requirements.

What is the best way to monitor replica lag in a mixed-mode MySQL replication topology?

Monitoring replica lag in mixed-mode topologies involves tracking GTID positioning and applying operational best practices. This identifies replication delays across Async, GTID, and semi-sync modes to maintain failover readiness.

Can I migrate between asynchronous and Group Replication modes in Percona Server 8.4?

You can migrate between asynchronous and Group Replication modes in Percona Server 8.4. This requires version-aware guidance to adapt to 8.4 syntax changes and ensure binlog behavior matches the target topology.

Does Percona Server for MySQL 8.4 change syntax for configuring high availability failover?

Percona Server for MySQL 8.4 introduces syntax adaptations affecting high availability failover procedures. Configuring replication topologies requires applying version-aware best practices for binlog behavior and GTID positioning.