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

Modify ResourceYielder of MultiStatementTransactionRequestsSender for shards

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19

      During a $lookup pipeline construction we first attempt to build a pipeline using local information. If we fail to do so we assume we'll have to contact a remote shard.

      Doing so ends up calling MultiStatementTransactionRequestsSender via CursorEstablisher.

      However, in case we're inside a multi-document transaction we aren't releasing the checked out session on the originating shard. As a result, we'd end up deadlocking the operation if the collection exists on the originating shard again as they could end up contacting themselves and waiting for a checked out session.

            Assignee:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Reporter:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: