SERVER-82180 added an assertion that any writer to a non-clustered capped collection that has oplog slots reserved must have already acquired the resource lock. Currently, this lock is not acquired here when applying a batch of inserts to a capped collection on a secondary. This missing lock acquisition shouldn't pose any insertion order issues, since any writes to a capped collection would be batched within the same batch and be serialized, but we should add the lock acquisition here in order to satisfy the assertion and then revisit it in SERVER-106004