mydumper/mydumper

Official MyDumper Project

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 21st, 2026
Created on November 6th, 2015
Open Issues & Pull Requests: 57 (+0)
GitHub issues: Enabled
Number of forks: 517
Total Stargazers: 3,234 (-1)
Total Subscribers: 78 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.7 hours
Mean response time: 25.2 days
90th percentile: 51.9 days
Tracked items: 378

How this project is maintained

About 12% of issues opened in the past year have never received a reply. 61% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "Question" is answered fastest, typically in about 4 hours, while "Feature Request" waits about 8 days. 71% of issues opened in the past year have been closed, leaving a working backlog. Three people close 89% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 54
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 333 days
Stale 30+ days: 41
Stale 90+ days: 28

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Bug (139)
  • Enhancement (105)
  • Help Wanted (77)
  • Feature Request (46)
  • Question (39)
  • Test case needed (19)
  • Duplicate (14)
  • Invalid (14)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

MyDumper is a MySQL logical backup tool that exports consistent database snapshots and imports them using multithreading for parallelism.

The tool addresses the need for fast, manageable MySQL backups by splitting the export and import process across multiple threads. MyDumper exports databases to separate files for each table along with metadata, while MyLoader reads these backups and imports them into a destination database. Consistency is maintained through a snapshot mechanism that acquires a global read lock, reads metadata about master and slave positions, and establishes transactional snapshots across worker threads before releasing the lock and beginning the actual dump work. This approach avoids expensive character set conversion routines and produces output that is easier to parse and manage than monolithic dumps.

MyDumper suits teams running MySQL, MariaDB, Percona, or TiDB who need faster backups than single-threaded tools provide and want finer control over what gets backed up. The tool supports PCRE regular expressions for including or excluding specific databases and tables. It handles Aurora and MySQL 5.7 environments with specific configuration options. Anyone considering adoption should be aware that consistent snapshots currently work only for transactional storage engines, with support for non-transactional engines noted as expected in future releases.

The project maintains active development with regular updates to its documentation and build infrastructure. The tool is community-maintained rather than backed by MySQL, Percona, or MariaDB. Official Docker images are provided for both development builds and quick deployment scenarios. The codebase includes machine-readable JSON logging output for integration with monitoring systems.