[SERVER-33698] batchSize:0 snapshot reads must allocate a WiredTiger transaction Created: 06/Mar/18 Updated: 29/Oct/23 Resolved: 15/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | James Wahlin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Storage NYC 2018-03-26, Storage NYC 2018-03-12 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
We currently open WiredTiger transactions in a lazy manner. As batchSize:0 reads do not need to access collection data, we do not start a WiredTiger transaction until the subsequent getMore. For readConcern level snapshot reads this is counter-intuitive and allows for reading of writes that occur in-between the find and getMore. |
| Comments |
| Comment by Githook User [ 15/Mar/18 ] |
|
Author: {'email': 'james@mongodb.com', 'name': 'James Wahlin', 'username': 'jameswahlin'}Message: |