[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:
Related
is related to SERVER-39751 Investigate the case when transaction... Closed
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 "SERVER-39750 remove unused function repl::getNextOpTimeNoPersistForTesting()"

This reverts commit dcd206284f4a106c3140a9a30a6b6d625cac2e0e.
Branch: master
https://github.com/mongodb/mongo/commit/f947d890558f627197eb2303f4bed799345f9d72

Comment by Githook User [ 24/Apr/19 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-39750 remove unused function repl::getNextOpTimeNoPersistForTesting()

The last reference to this function was removed in commit da63637defad5975040f8eac0e98c86c8d8e2533.
Branch: master
https://github.com/mongodb/mongo/commit/dcd206284f4a106c3140a9a30a6b6d625cac2e0e

Comment by Githook User [ 16/Apr/19 ]

Author:

{'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}

Message: SERVER-39750 add JS test for inducing cache pressue using a large unprepared transaction
Branch: master
https://github.com/mongodb/mongo/commit/eb038252f9fea34d03d0d8f80eca3eea1d35c9aa

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 SERVER-33191.

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.

Generated at Thu Feb 08 04:52:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.