[DOCS-867] improve concurrency faq Created: 10/Dec/12 Updated: 10/Dec/12 Resolved: 10/Dec/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Blocker - P1 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: http://docs.mongodb.org/manual/faq/concurrency/ |
||
| Participants: | |
| Days since reply: | 11 years, 10 weeks, 2 days ago |
| Description |
|
First question complicates the answer by mixing locking behavior and granularity of locks. This should be split out, and lock def. should link to wikipedia page with better description in wiki docs. Yielding happens for more than disk access (which was added in 2.0 and expanded in 2.2). Multiple document writes yield as well as readers, periodically. This can allow reads during long (multi-doc) write operations. And there are more issues here... so it is best if this put back on the list for more review. |
| Comments |
| Comment by auto [ 10/Dec/12 ] |
|
Author: {u'date': u'2012-12-10T17:27:16Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: |
| Comment by auto [ 10/Dec/12 ] |
|
Author: {u'date': u'2012-12-10T16:45:33Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: |
| Comment by auto [ 10/Dec/12 ] |
|
Author: {u'date': u'2012-12-10T16:00:17Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: |
| Comment by Sam Kleinman (Inactive) [ 10/Dec/12 ] |
|
Scott, thanks for the catch, I'll get a rev out this morning and we can mop up the remainder of the unspecified issues. http://www.mongodb.org/pages/viewpage.action?pageId=54624264 |