replication-manager
A high-availability orchestrator for MySQL, MariaDB, and Percona Server replication topologies with automated failover, backup, and proxy integration.
What is replication-manager?
Replication Manager is a high-availability orchestrator designed for MariaDB, MySQL, and Percona Server replication environments. It ensures database continuity through automated failover, switchover, and recovery processes, making it essential for production systems requiring minimal downtime and data loss.
Database administrators and DevOps engineers managing production MariaDB, MySQL, or Percona Server replication clusters who need automated high-availability solutions. Organizations running critical database workloads that cannot tolerate extended downtime.
Developers choose Replication Manager for its comprehensive feature set that goes beyond basic failover, including backup/recovery, proxy integration, and security features like credential rotation. Its emphasis on near-zero data loss and support for diverse replication topologies (async, semi-sync, multi-master, group replication) makes it suitable for complex production environments.
Overview
Signal 18 repman - Replication Manager for MySQL / MariaDB / Percona Server
Use Cases
Best For
- Automating failover and switchover processes in MariaDB/MySQL replication clusters to minimize downtime during primary failures
- Managing multi-cluster database environments from a single orchestration instance with centralized control
- Integrating database high-availability with proxy layers like ProxySQL, MaxScale, and HAProxy for complete stack automation
- Implementing comprehensive backup strategies with logical/physical backups and point-in-time recovery using tools like Restic
- Enhancing database security operations with credential rotation, HashiCorp Vault integration, and encrypted configuration secrets
- Deploying database high-availability solutions on Kubernetes or OpenSVC with proper service orchestration
Not Ideal For
- Environments using databases outside the MariaDB/MySQL/Percona ecosystem (e.g., PostgreSQL, MongoDB)
- Small, single-replica setups where the orchestration overhead outweighs the high-availability benefits
- Teams fully reliant on cloud-managed database services (e.g., AWS RDS, Google Cloud SQL) with built-in failover
Pros & Cons
Pros
Supports GTID, multi-source, delayed replication, and detects various topologies including async, semi-sync, multi-master, and group replication, as per the README, ensuring compatibility with complex production setups.
Provides controlled promotion and automatic primary election with near-zero data loss targeting, essential for minimizing downtime during database failures, as highlighted in the key features.
Offers logical backups via mysqldump/mydumper and physical backups via mariabackup/xtrabackup, with snapshot backups and point-in-time recovery using Restic and S3 storage, detailed in the backup section.
Automates backend management for proxies like ProxySQL and MaxScale, and includes credential rotation with Vault integration and OAuth2 SSO, enhancing operational security and efficiency.
Cons
Features multi-layer config inheritance and encrypted secrets, which can be daunting to set up correctly without deep database administration expertise, as indicated in the operations section.
Only compatible with MariaDB, MySQL, and Percona Server, excluding other databases like PostgreSQL or NoSQL systems, limiting its use in heterogeneous environments.
Requires integration with multiple external tools (e.g., proxies, backup systems, Vault), increasing maintenance burden and potential points of failure, as seen in the proxy and security features.
Frequently Asked Questions
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.