[SERVER-38436] Add concurrency workload for majority writes concurrent with prepared transactions Created: 06/Dec/18  Updated: 29/Oct/23  Resolved: 21/Mar/19

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

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done after SERVER-39074 Update outside transaction erasing up... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-12-31, Sharding 2019-01-14, Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25, Sharding 2019-03-11, Sharding 2019-03-25
Participants:

 Description   

The presence of prepared transactions currently holds back the committed snapshot, which prevents satisfying majority write concern for concurrent operations. These operations should eventually succeed once the prepared transactions commit or abort, and a concurrency workload should be added to verify this assumption.



 Comments   
Comment by Githook User [ 21/Mar/19 ]

Author:

{'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow', 'username': 'jsmulrow'}

Message: SERVER-38436 Add concurrency workload for majority writes alongside transactions
Branch: master
https://github.com/mongodb/mongo/commit/8284b68fd265df73ab60f15f97ae3ada145f49d2

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