Don't lock session catalog to find highest child txnNumber to refresh transaction participant

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.0.0-rc9, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v6.0
    • Sharding NYC 2022-06-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently a transaction participant will get the highest txnNumber the SessionCatalog has seen for any transaction in the current logical session when refreshing the participant from disk. This is to avoid reading more config.transactions entries than necessary. This is gotten from the SessionRuntimeInfo of the participant's session from the SessionCatalog. By this point, the participant has already checked out the session once, so we should be able to avoid looking back into the SessionCatalog (and locking its mutex) by caching the highest seen txnNumber onto the participant's Session, which is accessible directly in the transaction participant code.

            Assignee:
            Jack Mulrow
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: