[SERVER-24629] Add concurrency protection to MetadataManager Created: 16/Jun/16  Updated: 19/Jul/16  Resolved: 06/Jul/16

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

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

Backwards Compatibility: Fully Compatible
Sprint: Sharding 16 (06/24/16), Sharding 17 (07/15/16)
Participants:

 Description   

Add a private mutex to the MetadataManager class, and lock it at the start of functions.

Please add an invariant to the MetadataManager destructor that _activeMetadata is either unset or its usageCounter is zero.



 Comments   
Comment by Githook User [ 06/Jul/16 ]

Author:

{u'username': u'leonz', u'name': u'Leon Zaruvinsky', u'email': u'leon@mongodb.com'}

Message: SERVER-24629 Add concurrency protection to MetadataManager
Branch: master
https://github.com/mongodb/mongo/commit/a05bea91482fa70583680596823a115293d9d9a6

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