[DOCS-7317] Concurrent modifications can cause results to be missed from scans even under 3.2/WT Created: 01/Mar/16 Updated: 14/Mar/16 Resolved: 14/Mar/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 48 weeks, 2 days ago | ||||||||
| Description |
|
https://docs.mongodb.org/manual/faq/concurrency/#what-isolation-guarantees-does-mongodb-provide
This is not specific to MMAPv1 - it applies to WT as well. |
| Comments |
| Comment by Githook User [ 14/Mar/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 14/Mar/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |