Description
There should be a way to specify a write concern to be used after every insert in a copydb command, otherwise it's possible to overrun replication on the destination set, causing the secondaries to be too stale to catch up.
There should be a way to specify a write concern to be used after every insert in a copydb command, otherwise it's possible to overrun replication on the destination set, causing the secondaries to be too stale to catch up.