[SERVER-52972] Handle SnapshotUnavailable and LockTimeout errors when running transaction to drop a role Created: 20/Nov/20  Updated: 29/Oct/23  Resolved: 11/Feb/21

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

Type: Bug Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Sara Golemon
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Security 2020-12-14, Security 2020-12-28, Security 2021-01-11, Security 2021-01-25, Security 2021-02-08, Security 2021-02-22
Participants:
Linked BF Score: 33

 Description   

SERVER-49931 added a change to drop a role inside of a transaction. We should consider retrying the transaction if it fails due to a transient reason like SnapshotUnavailable or a LockTimeout.

These errors are pretty likely to occur as other operations in the system are running. For example, an index build on the admin.system.users collection right after the read timestamp for the transaction was established could cause the snapshot to become unavailable.



 Comments   
Comment by Githook User [ 11/Feb/21 ]

Author:

{'name': 'Sara Golemon', 'email': 'sara.golemon@mongodb.com', 'username': 'sgolemon'}

Message: SERVER-52972 Retry drop role transactions in UMC command
Branch: master
https://github.com/mongodb/mongo/commit/8aea774eb7a9bb4774dcd202eef97814a9a46cc6

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