[DOCS-5078] Concurrency FAQ for 3.0 is not up-to-date on locking in 3.0 Created: 23/Mar/15 Updated: 11/Jan/17 Resolved: 23/Mar/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Berkeley | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 8 years, 47 weeks, 2 days ago |
| Description |
|
In these sections of the concurrency FAQ: http://docs.mongodb.org/manual/faq/concurrency/#what-type-of-locking-does-mongodb-use http://docs.mongodb.org/manual/faq/concurrency/#how-granular-are-locks-in-mongodb The information is not up to date on locking with 3.0 and WiredTiger, since mmapv1 now offers collection-level locking and WiredTiger offers document-level locking. It's vexing because this FAQ is where we point community members with basic questions about concurrency like "can I write to collection x and y at the same time in 3.0?" (Pardon if this is a duplicate- seems like it should've been picked up by now but a search didn't turn it up) |