[SERVER-70408] Migrations for collection undergoing range deletion must not stall in v6.0 Created: 10/Oct/22 Updated: 30/Nov/22 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Tommaso Tocci |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
Thanks jordi.serra-torrens@mongodb.com for reporting this. On v6.0, the ScopedRangeDeleter lock is held while executing the range deletion for a collection C. This lock takes this RESOURCE_MUTEX in MODE_X. This can lead to stalling concurrent migrations on collection C here, or here, or here until the range deletion task ends. |
| Comments |
| Comment by Tommaso Tocci [ 01/Nov/22 ] |
|
Fixed by |