As a part of the PM-1950 shardCollection will generate an entry in the oplog on the primary shard. The oplog entry will use the “no-op” type. This way,it is still going to be replicated, but result in no work being done by secondaries as part of oplog application (even in older versions of MongoDB). Writing this no-op entry should happen before deleting the state document corresponding to the operation.
- is depended on by
-
SERVER-63437 Expose all events on 'system.resharding.*' collections when 'showSystemEvents' is true
-
- Closed
-
-
SERVER-61888 Add shardCollection change stream event
-
- Closed
-
- related to
-
SERVER-64542 shardCollection no-op oplog can be written even when command ultimately fails
-
- Closed
-