[SERVER-65015] Granular locks for synchronizing orphans tracking Created: 29/Mar/22  Updated: 29/Oct/23  Resolved: 26/Apr/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc4, 6.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0
Sprint: Sharding EMEA 2022-05-02
Participants:

 Description   

SERVER-64163 introduced a generic lock on the range-deleter collection for synchronizing orphans update and range deletions. Purpose of this ticket is to implement a more granular locking mechanism in order to parallelize concurrent orphans updates and range deletions. The granularity could be at range level (very granular, lock by migrationId) or at least at collection level (less granular, lock by collection UUID).



 Comments   
Comment by Githook User [ 03/May/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-65015 Granular locks for synchronizing orphans tracking
Branch: v6.0
https://github.com/mongodb/mongo/commit/a2958974d420a6cd7ac1b3230ff8cb6581115578

Comment by Githook User [ 26/Apr/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-65015 Granular locks for synchronizing orphans tracking
Branch: master
https://github.com/mongodb/mongo/commit/5e160450d659437dc7455c0138dfa0667ab091b6

Generated at Thu Feb 08 06:01:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.