# Percona ClusterSync for Mongodb Feedback

**URL:** https://forums.percona.com/t/percona-clustersync-for-mongodb-feedback/39505
**Category:** Percona ClusterSync for MongoDB (PCSM)
**Created:** [October 7, 2025, 5:45am UTC](https://forums.percona.com/t/percona-clustersync-for-mongodb-feedback/39505 "2025-10-07T05:45:50Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Semantic](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/semantic/32/9104_2.png) [@Semantic](https://forums.percona.com/u/Semantic)
#### Post date: [October 7, 2025, 5:45am UTC](https://forums.percona.com/t/percona-clustersync-for-mongodb-feedback/39505/1 "2025-10-07T05:45:50Z")

</div>

Wanted to give a bit of feedback to you guys on percona-link-mongodb. It’s really useful to migrate small/medium clusters (even cross region) and avoids having to deal with the whole backup and restore process.

I did however have to [fork it](https://github.com/balthazar/percona-link-mongodb) in order to increase a timeout due to my cluster being quite large as it would otherwise fail on the 5 minutes hardcoded value.

It also acted a bit strange processing an oplog as it was only doing cycles of network burts every hour or so for 10-15min and then stopped without much disk or CPU activity which made it extra slow to catchup. This particular cluster does a lot of writes and has a TTL index doing auto deletes, which could be a reason why it acted that way.

Given this slow oplog processing which might be a bug or a quirk for this specific cluster, I didn’t end up trying it on my bigger (~1TB wiredtiger) clusters migrations and opted for a physical restore, but overall great tool!

Cheers!

@radoslaw.szulgo @daniil.bazhenov

---

<div class="post-metadata">

### Author: ![Inel\_Pandzic](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/inel_pandzic/32/23166_2.png) [@Inel\_Pandzic](https://forums.percona.com/u/Inel_Pandzic)
#### Post date: [October 8, 2025, 11:34am UTC](https://forums.percona.com/t/percona-clustersync-for-mongodb-feedback/39505/2 "2025-10-08T11:34:14Z")

</div>

Hey @Semantic

Really appreciate the feedback from you. Yes, currently replication performance is not what we are happy about and we have a task to improve it, we know what is the bottleneck. Hopefully in 0.8.0 we could have this improvement.

Regarding the timeout, I’ll create a task to make it configurable, that’l make it a bit easier to override rather than a fork 🙂

Again, thanks for the feedback, it helps us a lot to make PLM better.

Cheers,

Inel

---

<div class="post-metadata">

### Author: ![Semantic](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/semantic/32/9104_2.png) [@Semantic](https://forums.percona.com/u/Semantic)
#### Post date: [October 8, 2025, 12:58pm UTC](https://forums.percona.com/t/percona-clustersync-for-mongodb-feedback/39505/3 "2025-10-08T12:58:51Z")

</div>

Glad that helped 😃

I could make a PR if the implementation is satisfying for you guys, no worries if not

---

<div class="post-metadata">

### Author: ![Inel\_Pandzic](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/inel_pandzic/32/23166_2.png) [@Inel\_Pandzic](https://forums.percona.com/u/Inel_Pandzic)
#### Post date: [October 8, 2025, 1:58pm UTC](https://forums.percona.com/t/percona-clustersync-for-mongodb-feedback/39505/4 "2025-10-08T13:58:12Z")

</div>

Please do, that would be awesome 🙂

I believe your implementation is good, but I something comes up, we can discuss it in the PR.

Thanks!
