[SERVER-72290] `deleteRangeDeletionTasksForRename` must not deregister tasks for the target collection Created: 20/Dec/22 Updated: 29/Oct/23 Resolved: 09/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc5, 6.3.0-rc0 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v6.2
|
||||
| Sprint: | Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09 | ||||
| Participants: | |||||
| Description |
|
When renaming a sharded collection, each participant shard is executing some code aimed at copying existing range deletion documents from the source namespace to the target namespace. Subsequently, this code is executed to delete range deletion documents referring the old namespace. The range deleter service observer is reacting by deregistering the range deletion task for each deleted document: since renaming preserves collection UUIDs, this results in wrongly deregistering range deletion tasks belonging to the target collection. As the new range deleter service lands in v6.2, the release candidate is the only version affected at the time of writing this ticket. |
| Comments |
| Comment by Githook User [ 09/Jan/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 09/Jan/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |