[SERVER-44156] Submit tasks to the CollectionRangeDeleter when config.rangeDeletions is updated Created: 22/Oct/19 Updated: 29/Oct/23 Resolved: 31/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Alexander Taskov (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2019-11-04 |
| Participants: |
| Description |
|
In the ShardServerOpObserver::onUpdates function, if we observe an update to config.rangeDeletions removing the "prepare" field, we should call CollectionShardingRuntime::cleanupRange for the range specified in the document. We can test this independently with a jstest:
|
| Comments |
| Comment by Githook User [ 31/Oct/19 ] |
|
Author: {'username': 'alextaskov', 'email': 'alex.taskov@mongodb.com', 'name': 'Alex Taskov'}Message: |