[SERVER-48539] CollectionIndexUsageTracker must have its own concurrency control without depending on collection level locking Created: 02/Jun/20  Updated: 29/Oct/23  Resolved: 19/Aug/20

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-06-15, Execution Team 2020-06-29, Execution Team 2020-07-13, Execution Team 2020-07-27, Execution Team 2020-08-24
Participants:

 Description   

Per the Lock Free Reads project, collection level locking concurrency control will change, removing read collection IS locks, so reads will no longer conflict with X lock index operations. This will make the internal usage of CollectionIndexUsageTracker's map unsafe.

Need some new concurrency control in CollectionIndexUsageTracker



 Comments   
Comment by Githook User [ 19/Aug/20 ]

Author:

{'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}

Message: SERVER-48539 Add internal concurrency control to CollectionIndexUsageTracker
Branch: master
https://github.com/mongodb/mongo/commit/6ffbf7c475ee34575a632040b70a6a20aa13cb4a

Generated at Thu Feb 08 05:17:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.