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

Session catalog migration will skip later sessions if a different earlier session encounters new transaction

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.10, 4.0.5, 4.1.7
    • Affects Version/s: 3.6.9, 4.0.4
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • Sharding 2018-12-17

      Migration of the sessions catalog needs to be prepared to find a new transaction already started on the recipient shard for an older session it is migrating from the donor. Because of the place where this try/catch block is placed though, such a condition will skip all the sessions that follow, meaning that there will be incomplete session information on the recipient shard.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: