Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-76749

runTransactionOnShardingCatalog should not assign the current operation context session id to the new operation context

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 7.0.0-rc1
    • Affects Version/s: 7.0.0-rc0, 7.1.0-rc0
    • Component/s: None
    • None
    • Fully Compatible
    • v7.0
    • Sharding EMEA 2023-05-15

      Right now the runTransactionOnShardingCatalog assigns the operation context 's session id to the new operation context in case the input osi is empty.

      This is wrong becauseĀ 

      • a user would naturally expect to assign an empty osi in case of empty input osi
      • passing the operation context session id will end up in a dead lock if the session was already checked outĀ 

            Assignee:
            enrico.golfieri@mongodb.com Enrico Golfieri
            Reporter:
            enrico.golfieri@mongodb.com Enrico Golfieri
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: