Direct modifications to config.transactions can potentially bump txnNumber even when in prepared state

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When a transaction transitions to prepared state, it is not allowed to bump to txnNumber. This is achieved by using a lock on the txnNumber. However, there is a loop hole where it is possible to directly modify the config.transactions document which causes the in-memory structure to become invalidated and load from storage.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: