[DRIVERS-2049] Reinstate readConcern snapshot test on sharded cluster after 4.2.1 is released Created: 10/Sep/19  Updated: 31/Mar/22

Status: Backlog
Project: Drivers
Component/s: Transactions
Fix Version/s: None

Type: Spec Change Priority: Major - P3
Reporter: Shane Harvey Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Driver Changes: Needed

 Description   

In SPEC-1411 we removed testing of read concern snapshot on sharded clusters. However in HELP-10518, dianna.hohensee mentions that SERVER-42205 might help avoid these snapshot errors so once 4.2.1 is released we can try reinstate the snapshot test(s). Basically we should revert part (or all) of the changes in SPEC-1411 and see if the tests pass.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 12/Dec/19 ]

shane.harvey, no, the server has not been updated since the resolution of WT-5124. I believe further server work still must be done – though SERVER-42205 may have mitigated (dubious about eliminated) the problem for the Drivers tests. There is not currently any ticket to follow for that work: we do not currently have consensus about what to do among the interested parties.

Comment by Shane Harvey [ 10/Dec/19 ]

dianna.hohensee, from WT-5124 it looks like we realized that the server was using the incorrect metric to estimate cache pressure. Was the server updated to use a different approach? Do you think 4.2.2 will have resolved this issue?

Comment by Esha Bhargava [ 09/Dec/19 ]

shane.harvey4.2.1 is out. Test this when you get a chance to.

Comment by Dianna Hohensee (Inactive) [ 16/Sep/19 ]

Yes, SERVER-42205 could have had an effect. Otherwise, if it doesn't, you'll probably be interested in the outcome of WT-5124.

Generated at Thu Feb 08 08:24:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.