MongoShake is a universal data replication platform based on MongoDB's oplog. Redundant replication and active-active replication are two most important functions. 基于mongodb oplog的集群复制工具，可以满足迁移和同步的需求，进一步实现灾备和多活功能。
active 2025-03-09 → 2026-06-22 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 471 days from 2025-03-09 to 2026-06-22. Pushes: 9 total, peak 1 in a day. Pull requests: 26 total, peak 11 in a day. Issues: 77 total, peak 12 in a day. Comments: 116 total, peak 9 in a day. Stars: 30 total, peak 1 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| zhongli-james | 154 | 9 | 9 | 76 |
| dependabot[bot] | 13 | 0 | 13 | 0 |
| Julieti | 8 | 0 | 0 | 6 |
| SisyphusSQ | 6 | 0 | 1 | 5 |
| Steloj-shaw | 5 | 0 | 0 | 4 |
| pengzhenyi2015 | 5 | 0 | 0 | 3 |
| mrnonz | 3 | 0 | 3 | 0 |
| Nin0306 | 2 | 0 | 0 | 1 |
| TheThirdReich77 | 2 | 0 | 0 | 0 |
| longjiquan | 2 | 0 | 0 | 0 |
| dobesv | 2 | 0 | 0 | 1 |
| zshyunjisuan | 2 | 0 | 0 | 1 |
| gzf1234 | 2 | 0 | 0 | 2 |
| CLAassistant | 2 | 0 | 0 | 2 |
| NaShenFu | 2 | 0 | 0 | 1 |
| tyj672372 | 2 | 0 | 0 | 1 |
| cbonilla-liquid | 2 | 0 | 0 | 1 |
| xdjiang | 2 | 0 | 0 | 2 |
| wonsikin | 2 | 0 | 0 | 2 |
| ViolaElrics | 1 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#976zhongli-james2026-06-22 01:58Incremental Oplog Application Fails After Setting oplog_store_disk=true
- Issue comment#979zhongli-james2026-06-09 03:03persister.retrieve() polling-based wait has 3s latency and leaks ticker after exit
- Issue comment#973ccfuncy2026-05-21 03:23Add configurable skip rules for duplicate insert conflicts after insert-on-dup update fallback
- Issue#934zhongli-james2026-05-13 06:22DDL 和DML操作没有按照oplog顺序同步，导致源库和目标库数据不一致
- Pull request#972zhongli-james2026-05-12 01:57
- Pull request#972zhongli-james2026-05-11 05:58
- Pull request#971mrnonz2026-05-09 04:39
- Pull request#970mrnonz2026-05-09 04:32
- Issue#930zhongli-james2026-04-28 07:48源库同步到目标库需要具备哪些权限、目前我大概只知道这些、不知道对不对、可以补充一下嘛、谢谢
- Releasezhongli-james2026-04-28 07:42release-v2.8.8-20260428
- Issue comment#965SisyphusSQ2026-04-21 02:24支持 master_quorum 自定义选主 ObjectId 并补齐配置校验
- Issue comment#897zhongli-james2026-04-20 01:27有集合a，类型为timeseries，数据库同时中存在system.buckets.a的集合，则启动mongoshake开始同步之后，同步到该集合会报错: get next document failed: run find failed: (BadValue) error processing query: ns=dr-test.system.buckets.aTree:
- Pull request#964zhongli-james2026-04-19 14:56
- Issue#874zhongli-james2026-04-17 09:59数据冷热备份方案
- Issue comment#959SisyphusSQ2026-04-17 09:52重构：将日志 SDK 替换为 zap，并统一日志调用方式
- Issue comment#959SisyphusSQ2026-04-16 09:32重构：将日志 SDK 替换为 zap，并统一日志调用方式
- Issue#960TheThirdReich772026-04-15 06:58Conf.Options check failed: connect source mongodb failed[no reachable servers]
- Issue#960TheThirdReich772026-04-15 02:11Conf.Options check failed: connect source mongodb failed[no reachable servers]
- Issue#959zhongli-james2026-04-15 02:02重构：将日志 SDK 替换为 zap，并统一日志调用方式
- Issue#959zhongli-james2026-04-15 02:00重构：将日志 SDK 替换为 zap，并统一日志调用方式
- Issue#958zhongli-james2026-04-14 09:57我用mongoshake迁移数据，mongo版本是7.0 一直提示auth failed
- Pull request#957SisyphusSQ2026-04-14 06:51
- Issue#956zhongli-james2026-04-14 02:39Inconsistent checkpoint/status and syncing behavior after CappedPositionLost (MongoShake v2.8.7)
- Pull request#953mrnonz2026-04-13 02:40
- Issue comment#949SisyphusSQ2026-03-30 02:15Support filtering oplog by op type with filter.cmds
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 30 stars here means stars gained during the window, not the repo's star count.