[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: |
|
||||||||||||||||||||
| 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: |