[DOCS-474] Documentation on concurrency doesn't include information on concurrency in r2.2 Created: 31/Aug/12 Updated: 10/Dec/12 Resolved: 08/Dec/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Zola | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 11 years, 10 weeks, 2 days ago | ||||
| Description |
|
Documentation should cover concurrency and locking information for MongoDB 2.2. This should probably include a table indicating the lock level required for various operations. |
| Comments |
| Comment by auto [ 10/Dec/12 ] |
|
Author: {u'date': u'2012-12-08T20:12:07Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: |
| Comment by Sam Kleinman (Inactive) [ 08/Dec/12 ] |
|
added a couple of version changed notes. The manual explicitly documents 2.2.x+, and will note when things were introduced in 2.x (and in some cases 2.0, for some behaviors) but to provide consistency, will not (and should not) document previous behavior to prevent confusion and abstruse information presentation... |
| Comment by William Zola [ 07/Dec/12 ] |
|
I note that both these sections have paragraphs marked 'changed in version 2.2':
Since folks will be using 2.0 for some time to come, I think that these are a good idea. I don't see why this shouldn't apply to the section on replication as well. |
| Comment by Scott Hernandez (Inactive) [ 07/Dec/12 ] |
|
The manual is versioned at the current version (2.2+) and we are not writing versions for old releases. |
| Comment by William Zola [ 07/Dec/12 ] |
|
Information in the last section ( http://docs.mongodb.org/manual/faq/concurrency/#how-does-concurrency-affect-secondaries) is correct for version 2.2, but not correct for version 2.0. In version 2.0, operations are read individually off the oplog and applied serially to the secondary. |
| Comment by Sam Kleinman (Inactive) [ 07/Dec/12 ] |