[SERVER-34650] Write test for transaction write conflicts with non-transactional writes Created: 24/Apr/18  Updated: 29/Oct/23  Resolved: 15/May/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

Type: Task Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-34648 Write test for all types of transacti... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-05-07, Repl 2018-05-21
Participants:
Story Points: 4

 Description   

We want to test the behavior write conflicts between multi-statement transactions and writes outside of multi-statement transactions. We should test the following cases:

  1. Start a transaction T. then, outside of the transaction, update document D. Then try to write to document D from within transaction T and verify a write conflict occurs.
  2. Start a transaction T and write to document D. Then try to do a non-transactional update to D. Verify that this non-transactional write blocks until the transaction has committed, or until maxTimeMS expires.


 Comments   
Comment by Githook User [ 15/May/18 ]

Author:

{'email': 'william.schultz@mongodb.com', 'username': 'will62794', 'name': 'William Schultz'}

Message: SERVER-34650 Test write conflict behavior between transactional and non-transactional writes
Branch: master
https://github.com/mongodb/mongo/commit/1e1dbf625f6a670487151c82fd40f1809ec084e1

Comment by Tess Avitabile (Inactive) [ 02/May/18 ]

For case (1), we test this for update and delete inĀ  read_concern_snapshot_yielding.js.

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