FsyncLock

When You Need fsyncLock: Restoring a MongoDB Replica Set from Local Snapshots on Every FlashArray

In my reseed post, I spent a lot of time convincing you that you don’t need fsyncLock. One crash-consistent snapshot of the primary, replicated to every array, rebuilt every secondary in the set, under load, with no pause in writes. That’s still what I reach for when I’m rebuilding members.

Then I asked myself the obvious follow-up: what if I want to put every member back to the same known moment, each one from its own array’s local snapshot? That’s the one case in this series where I do reach for the lock. It’s also the Python version of my 2025 post on app-consistent snapshots across multiple FlashArrays, this time for a replica set instead of a sharded cluster.