[SERVER-2278] A locked mongod can't access a new database. Created: 22/Dec/10  Updated: 21/Mar/13  Resolved: 11/Jun/12

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

Type: Bug Priority: Major - P3
Reporter: Richard Kreuter (Inactive) Assignee: Dwight Merriman
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File mongod-lock.txt    
Issue Links:
Duplicate
duplicates SERVER-1423 reads often aren't possible while in ... Closed
Related
related to SERVER-4243 If there is a pending write due to an... Closed
Operating System: ALL
Participants:

 Description   

The first time mongod accesses a db, it takes a write lock. Consequently, if the database is locked before a particular db is accessed, the first client accessing that db will hang. Example attached.



 Comments   
Comment by auto [ 17/Jan/12 ]

Author:

{u'login': u'dwight', u'name': u'dwight', u'email': u'dwight@10gen.com'}

Message: SERVER-2278 recent changes to not do the unlock / relock with write lock if db not opened broke
REST if the db wasn't open - the admin db in particular. fix isn't super elegant because of the timeout stuff
otherwise would have been a one liner
Branch: master
https://github.com/mongodb/mongo/commit/e2adb6c54c58c6d63b97650e922fd951c43a2898

Comment by Dwight Merriman [ 15/Jan/12 ]

trying to parse the example.

are you saying that fsync+lock was in a write lock instead of a read lock? yes i believe that was the case. this is changing in 2.1 but in progress.

are there other cases like this because lock+fsync that come to mind?

Generated at Thu Feb 08 02:59:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.