When replicating document ops with doc-level-locking storage engines, we may batch apply operations in parallel within the same collection. If unique secondary indexes exist (that is, unique indexes other than id), their unique constraints may be temporarily violated during the application of a batch of ops. If this happens, the secondary node would detect this and shut down before data corruption resulted.
In order to fix this, we need to disable unique key checking while applying ops on secondaries.