Handle SnapshotUnavailable and LockTimeout errors when running transaction to drop a role

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: Security
    • None
    • Fully Compatible
    • ALL
    • Security 2020-12-14, Security 2020-12-28, Security 2021-01-11, Security 2021-01-25, Security 2021-02-08, Security 2021-02-22
    • 33
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Sara Golemon (Inactive)
            Reporter:
            Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: