[SERVER-67642] Investigate possibility of finer grade locking in range deleter service Created: 29/Jun/22  Updated: 05/Dec/22  Resolved: 14/Oct/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Do Votes: 0
Labels: pm-2849-optimizations
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-67635 Create range deleter service skeleton Closed
Related
related to SERVER-70586 Complete TODO listed in SERVER-67642 Closed
Assigned Teams:
Sharding EMEA
Participants:

 Description   

The initial version of the range deleter service will be implemented with global locking (one mutex protecting all the state). Purpose of this ticket is to investigate the possibility to use per-collection (per-UUID) locks within the service to avoid contention.



 Comments   
Comment by Githook User [ 21/Nov/22 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-70586 Complete TODO listed in SERVER-67642
Branch: master
https://github.com/mongodb/mongo/commit/e73b77b95a4aeda1de74839a2689dfcea932b9e0

Comment by Pierlauro Sciarelli [ 14/Oct/22 ]

Closing as "won't do" since the time this lock is held for any operation acquiring it is super-short.

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