Details
-
Improvement
-
Resolution: Done
-
Blocker - P1
-
None
-
None
-
None
-
*Location*: http://docs.mongodb.org/manual/faq/concurrency/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.91 Safari/537.11
*Referrer*: http://www.mongodb.org/display/DOCS/How+does+concurrency+work
*Screen Resolution*: 1920 x 1200
*Location*: http://docs.mongodb.org/manual/faq/concurrency/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.91 Safari/537.11 *Referrer*: http://www.mongodb.org/display/DOCS/How+does+concurrency+work *Screen Resolution*: 1920 x 1200
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.