Problem Statement/Rationale

Since any operation that modifies admin.system.version should error, when a move chunk occurs, it will generate an oplog like this:

Therefore, in a MongoDB cluster, whenever a moveChunk operation occurs, the oplog export will be terminated.

Steps to Reproduce

Step 1: Insert data into the db1.foo collection, with a sufficiently large amount of data.

Step 2: Use mongodump to export the oplog.

Step 3: Perform range sharding on the collection db1.foo.

After the above operations:

The mongodump process will exit because an oplog that modifies the admin.system.version collection has been generated.

Expected Results

The dump operation of the oplog should not be interrupted during the move chunk process.

Actual Results

What do you observe is happening?

Additional Notes

Any additional information that may be useful to include.