[SERVER-43384] Use non-snapshot read concern for sharded transaction in aggregation_currentop.js Created: 20/Sep/19  Updated: 29/Oct/23  Resolved: 24/Sep/19

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

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Alexander Taskov (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2
Sprint: Sharding 2019-10-07
Participants:
Linked BF Score: 35

 Description   

To test the $currentOp output for sharded transactions, sharding/aggregation_currentop.js starts a transaction through mongos using "snapshot" read concern, which can occasionally with SnapshotTooOld, which mongos can't retry on until SERVER-39704 is completed. The test doesn't rely on the particular read concern level of this transaction, so to avoid this problem the transaction can use a read concern level that does not require a global snapshot - majority, local, or none.



 Comments   
Comment by Githook User [ 02/Dec/19 ]

Author:

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

Message: SERVER-43384 Use non-snapshot read concern for sharded transaction in aggregation_currentop.js

(cherry picked from commit f66d468830246d4a448c9e87e698691e0abc026b)
Branch: v4.2
https://github.com/mongodb/mongo/commit/98ff3036a2157f0fed25bca81e55684acb5b9bd7

Comment by Githook User [ 23/Sep/19 ]

Author:

{'name': 'Alex Taskov', 'username': 'alextaskov', 'email': 'alex.taskov@mongodb.com'}

Message: SERVER-43384 Use non-snapshot read concern for sharded transaction in aggregation_currentop.js
Branch: master
https://github.com/mongodb/mongo/commit/f66d468830246d4a448c9e87e698691e0abc026b

Comment by Alexander Taskov (Inactive) [ 23/Sep/19 ]

https://mongodbcr.appspot.com/487660003/

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