initializeOperationSessionInfo should take the client lock while writing lsid

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.5.13
    • Affects Version/s: None
    • Component/s: Internal Code
    • None
    • Fully Compatible
    • ALL
    • Platforms 2017-09-11
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      initializeOperationSessionInfo is called without the client lock, which can cause it to do dirty partial writes to sessionId and txnNumber.

      This can cause data races with readers operating under the lock, causing them to see partial writes

            Assignee:
            Mira Carey
            Reporter:
            Mira Carey
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: