See: batch_executor.cpp::multiRemove()/multiUpdate(). The legacy write path is not necessarily affected as mongos no longer uses it.

If data has already been written these operations should not be aborted, and DeadlockExceptions can get thrown at any time during a multi-write.

Generally multi-writes are broadcast to all shards, but we should not rely on this behavior for correctness.