# openark/orchestrator

MySQL replication topology management and HA

Repository: https://github.com/openark/orchestrator
Canonical: https://ross.abutalabs.com/products/orchestrator
Language: Go
License: Apache-2.0
License Family: permissive
Topics: mysql, replication, high-availability, management-system
Archived: true
Last push: 2025-02-18T05:58:22+00:00

## Health v2 (maintenance only)
Score: 10/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 7, release rhythm 8, longevity 100
- inputs: {"age_days": 3563, "days_push": 561, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: archived
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 5775, forks 954 (observed 2026-08-28T04:09:29.489580+00:00)

## What it is
Orchestrator is a MySQL high availability and replication topology management tool that runs as a service with a web interface, HTTP API, and CLI. It discovers and visualizes replication topologies, enables safe replica refactoring, and performs automated master failure detection and recovery. The original repository is archived; maintenance continues via the Percona fork.

## Use cases
- manage mysql replication topology
- automated mysql master failover
- visualize database replication hierarchy
- recover from mysql master failure
- move replicas between masters safely
- monitor replication lag and problems

## When to choose
- you run MySQL replication and need HA with automated failover
- you want topology visualization and drag-and-drop replica refactoring
- you need Pseudo-GTID or GTID-based failover orchestration

## When to avoid
- you need actively maintained upstream software - the repo is archived; use the Percona fork instead
- you use a database other than MySQL
- you want a fully managed cloud HA solution rather than self-hosted tooling

## Facets
- artifact type: service
- maturity: abandoned
- function: database, monitoring, deployment, cli, web-framework
- domain: databases, self-hosted, monitoring
- platform: go, cli, self-hosted
- tags: mysql, replication, high-availability, failover, topology-management, archived, devops, linux, web-server

## Member repositories
- openark/orchestrator (main) score 10

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:09:29.489580+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:52:51.955945+00:00, confidence not recorded.
  - readme: https://github.com/openark/orchestrator (fetched 2026-08-28T04:09:29.489580+00:00, sha 0a1503965333)
- Data as of 2026-08-30T08:39:29.467469+00:00.