See context and issue details on BF-43757.

Background

In resharding_large_number_of_initial_chunks.js, a large number of predefined chunk data (100k chunks) is given to a reshard command.

Due to the changes in shard-authoritative, the kCreatingCollection phase now writes all chunk data for the recipient node. In this test, that's significant oplog impact on a small oplogSize (16MB) and the oplog rolls over and removes the minTimestamp oplog.

Then when the recipient later opens a change stream and searches for minTimestamp, it doesn't exist and OplogQueryMinTsMissing is thrown.

Fix

Increase the oplog size to 128 MB to ensure there is plenty of oplog space for the chunk data. The reproducer attached to the BF fails with an oplog size of 16 and succeeds with a size of 128 MB.