[SERVER-58767] Improve concurrency testing for transactions that do both reads and writes Created: 22/Jul/21  Updated: 12/Dec/23

Status: In Code Review
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-48366 Expand transactions atomicity isolati... Backlog
Assigned Teams:
Cluster Scalability
Sprint: Sharding 2021-08-23, Sharding 2021-09-06, Sharding 2021-09-20, Sharding 2021-10-04, Sharding 2021-10-18, Sharding 2021-11-01, Sharding NYC 2022-04-18, Sharding 2022-05-02, Sharding NYC 2022-05-16, Sharding NYC 2022-05-30, Sharding NYC 2022-06-13, Sharding 2022-06-27, Sharding 2022-07-11, Sharding 2022-07-25, Sharding 2022-08-08, Sharding 2022-08-22, Sharding 2022-09-05, Sharding 2022-09-19
Participants:
Story Points: 5

 Comments   
Comment by Jason Zhang [ 20/Jul/22 ]

Moving into PM-1632 since we expect to enable the optimization disabled in SERVER-48307. This ticket will give adequate coverage for that feature.

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