[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: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| 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: |
| 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? |