[SERVER-39750] Investigate the case when transaction size exceeds the cache size of WiredTiger Created: 21/Feb/19 Updated: 29/Oct/23 Resolved: 25/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | bigtxns_testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Storage NYC 2019-04-22, Storage NYC 2019-05-06 | ||||||||
| Participants: | |||||||||
| Comments |
| Comment by Githook User [ 25/Apr/19 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: Revert " This reverts commit dcd206284f4a106c3140a9a30a6b6d625cac2e0e. |
| Comment by Githook User [ 24/Apr/19 ] |
|
Author: {'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}Message: The last reference to this function was removed in commit da63637defad5975040f8eac0e98c86c8d8e2533. |
| Comment by Githook User [ 16/Apr/19 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: |
| Comment by Benety Goh [ 16/Apr/19 ] |
|
kelsey.schubert, as far as the JS test written for this ticket is concerned, the failure mode should resemble |
| Comment by Siyuan Zhou [ 15/Mar/19 ] |
|
Try large transactions that only modify a single document vs. multiple documents since WT will grow the page for the single document and behave differently. |
| Comment by Siyuan Zhou [ 15/Mar/19 ] |
|
It's also interesting to see how secondary batching and application logic handle very large transactions. |
| Comment by Kelsey Schubert [ 21/Feb/19 ] |
|
Ideally, the failure mode should include enough diagnostics for a user to determine what went wrong. |