[SERVER-5513] Locks per-ns while refreshing config data in mongod and mongos Created: 05/Apr/12  Updated: 05/Feb/16  Resolved: 21/Jul/15

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

Type: Improvement Priority: Major - P3
Reporter: Greg Studer Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

In many places it makes sense to not block ops on namespaces when refreshing the config data of another.



 Comments   
Comment by Kaloian Manassiev [ 21/Jul/15 ]

The catalog manager itself does not take any locks and every database and/or collection in the cache already has its own mutex, so this ticket is done.

Comment by Andy Schwerin [ 20/Jul/15 ]

kaloian.manassiev, is this likely to fall out of the work we're already doing on the catalog manager and cache? Or was this fixed in the past? Or neither?

Generated at Thu Feb 08 03:09:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.