[SERVER-33139] Abort mongoDB transactions when they try to use a storage engine txn and learn that it has been aborted Created: 06/Feb/18  Updated: 27/Oct/23  Resolved: 05/Apr/18

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Eric Milkie
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Comments   
Comment by Eric Milkie [ 05/Apr/18 ]

This behavior is already present and there is no further work to do here.

Comment by Spencer Brody (Inactive) [ 27/Mar/18 ]

I'm pretty sure this ticket is a no-op, because I think the way the storage engine signals this to MongoDB is by throwing a WriteConflictException, which we already handle.

milkie, can you confirm?

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