In batch_write_command_insert.js, we use remove({}) to get a collection back to its initial empty state. If the collection has a lot of elements in it (and we do at one point), then we end up deleting them all one by one on the secondaries, which puts a lot of load on the test infrastructure and causes spurious failures. We should drop the collection rather than remove({}) unless there's a good reason to do otherwise. It appears the remove({}) has been there since the test was created.