[SERVER-83440] Revert support for `fromMigrate` in batched delete stage Created: 20/Nov/23 Updated: 21/Nov/23 Resolved: 21/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | CAR Team 2023-11-27 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The support for fromMigrate in the batched deletes (introduced with The idea was to use batched delete in the range deleter, but after some testing we highlighted that this would increase latency causing an impact on the user's workload (see Additionally, this logic assumes the documents will not change during the migration, and it is not necessary to ensure they still match before deleting. There is concern this assumption is not valid, as users can connect directly to the shard. |
| Comments |
| Comment by Githook User [ 21/Nov/23 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |