[SERVER-48382] Change assertions in update_shard_key_conflicting_writes.js to be assert.soon Created: 21/May/20  Updated: 29/Oct/23  Resolved: 27/May/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Bug Priority: Major - P3
Reporter: Janna Golden Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-06-01
Participants:
Linked BF Score: 16

 Description   

After SERVER-37364 a transaction coordinator will return the commit decision as soon as the decision is persisted and majority committed. There are a number of cases in this test where we run a transaction in a parallel shell, and then make an assertion about the writes done in that transaction outside of the shell. Because this commit made it such that we may not see changes from a transaction without using a session with causal consistency for a bit, we should change any assertions to be an assert.soon. In particular this assertion should be changed (and we should double check for others!).



 Comments   
Comment by Githook User [ 27/May/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-48382 Change assertions in update_shard_key_conflicting_writes.js to be assert.soon
Branch: master
https://github.com/mongodb/mongo/commit/1ce8854a652e08d796621e268cc0c40ed1d56915

Generated at Thu Feb 08 05:16:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.