Secondary nodes can lag when a large number of DDL operations are replicated in rapid succession. For example, collection creation, building indexes on a very large number of small collections, and dropping a large number of collections and/or indexes.

This is due to our inability to parallelize these operations.  Leaving this ticket to reference as a known issue, and possibly look into what kinds of mitigation could be done for this.