[SERVER-61887] Add a no-op oplog entry for shardCollection command Created: 03/Dec/21  Updated: 29/Oct/23  Resolved: 22/Feb/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Nikita Lapkov (Inactive) Assignee: Misha Tyulenev
Resolution: Fixed Votes: 0
Labels: pm1950-m3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-63437 Expose all events on 'system.reshardi... Closed
is depended on by SERVER-61888 Add shardCollection change stream event Closed
Related
related to SERVER-64542 shardCollection no-op oplog can be wr... Closed
Backwards Compatibility: Fully Compatible
Sprint: QE 2022-02-07, QE 2022-02-21, QE 2022-03-07
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 22/Feb/22 ]

Author:

{'name': 'Misha Tyulenev', 'email': 'misha.tyulenev@mongodb.com'}

Message: SERVER-61887 add oplog noop event for shardCollection command
Branch: master
https://github.com/mongodb/mongo/commit/2de65e531b9c7ffb0af4202d98a774b7d3f53dfe

Generated at Thu Feb 08 05:53:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.