[DOCS-1364] Documentation doesn't indicate that db.fsyncLock() uses counters Created: 09/Apr/13 Updated: 30/Oct/23 Resolved: 01/Jul/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Trivial - P5 |
| Reporter: | Jeremy Mikola | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 10 years, 45 weeks, 1 day ago | ||||||||||||||||
| Description |
|
Multiple calls to db.fsyncLock() will require an equal number of calls to db.fsyncUnlock() to revert the database to a writable state. This is because the locks are tracked with counters, and it's not simply a boolean state (e.g. "am I locked or not"). It would be helpful if http://docs.mongodb.org/manual/reference/method/db.fsyncLock mentioned this. |