[SERVER-15647] Extent Manager must be Thread-safe Created: 14/Oct/14  Updated: 25/Oct/14  Resolved: 16/Oct/14

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

Type: Bug Priority: Major - P3
Reporter: Geert Bosch Assignee: Geert Bosch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File Design for thread-safe MMAPv1 Extent Manager (EM).txt    
Issue Links:
Depends
is depended on by SERVER-14674 Shard dies during chunk migration if ... Closed
is depended on by SERVER-15633 ShardingState::doRefreshMetadata shou... Closed
Tested
Operating System: ALL
Participants:

 Description   

In order to enable collection level locking for MMAPv1, the EM,
which is per-database, must handle concurrent read/write access
by operations on different collections.



 Comments   
Comment by Githook User [ 16/Oct/14 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-15647: make Extent Manager thread-safe and enable MMAPv1 CLL
Branch: master
https://github.com/mongodb/mongo/commit/6bc93c0a8730511e021645b711079dd0ec4e9f61

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