Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.7.4
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Repl 2018-04-09
Linked BF Score:
0
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

For multi-statement read-only (autocommit:false) transactions, we need to be able to commit/abort them to clean up the associated resources.

is duplicated by

SERVER-33681 Test and document behavior of running abortTransaction and commitTransaction against snapshot reads

Closed

is related to

SERVER-34038 Make sure that commitTransaction waits for writeConcern after a read-only transaction

Closed

Assignee:: Will Schultz
Reporter:: Spencer Brody (Inactive)
Participants:: Andy Schwerin, Githook User, Spencer Brody, Will Schultz
Votes:: 0 Vote for this issue
Watchers:: 11 Start watching this issue

Created:: Mar 20 2018 05:41:26 PM UTC
Updated:: Oct 29 2023 10:33:33 PM UTC
Resolved:: Apr 03 2018 11:49:35 PM UTC
Confidence Status Last Update:: 02/Apr/18 6:59 PM