[SERVER-34134] Wrap rollback database operations in WriteConflictRetry loops Created: 26/Mar/18  Updated: 29/Oct/23  Resolved: 11/Jun/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.0.0-rc5, 4.1.1

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Vesselina Ratcheva (Inactive)
Resolution: Fixed Votes: 1
Labels: neweng, rollback-optional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0
Sprint: Repl 2018-05-21, Repl 2018-06-04, Repl 2018-06-18
Participants:

 Description   

There are various operations in both RTT and rollback via refetch that don't use WriteConflictRetry loops. cappedTruncateAfter is one example. resetLastOpTimesFromOplog is another. WCE should not cause rollback to fail, which can be a long running operation to have to retry in full.



 Comments   
Comment by Githook User [ 11/Jun/18 ]

Author:

{'username': 'vessy-mongodb', 'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com'}

Message: SERVER-34134 Wrap rollback database operations in WriteConflictRetry loops

(cherry picked from commit 3a7e35704243c716222dfe5d4241bc73c4168484)
Branch: v4.0
https://github.com/mongodb/mongo/commit/3141f4f77f16158c2e4971d4e1f3fb2f7e4fd763

Comment by Githook User [ 11/Jun/18 ]

Author:

{'username': 'vessy-mongodb', 'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com'}

Message: SERVER-34134 Wrap rollback database operations in WriteConflictRetry loops
Branch: master
https://github.com/mongodb/mongo/commit/3a7e35704243c716222dfe5d4241bc73c4168484

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