[SERVER-67778] Lock collection via UUID rather than namespace in the range-deleter Created: 05/Jul/22 Updated: 29/Oct/23 Resolved: 27/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25, Sharding EMEA 2022-08-08 |
| Participants: |
| Description |
|
Change this AutoGetCollection to lock via db name + uuid rather than via namespace. As a consequence, simplify this check to only make sure a collection with the passed UUID still exists (no matter the namespace). Rationale: range deletions must be processed for a collection with a specific UUID independently from the namespace. This is a precondition to get rid in 7.1 of rename participants' special handling of range deletions. |
| Comments |
| Comment by Githook User [ 27/Jul/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |