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

Handle migration of sessions with incomplete history

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.0-rc2
    • Affects Version/s: 3.5.12
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2017-10-02, Sharding 2017-10-23, Sharding 2017-11-13

      because the oplog rolled over. This shouldn't cause the migration to fail, as this might just be a session that is too old that the user won't ever reference it again. However, the recipient shard should also have a way of knowing that it has accepted an incomplete history so when it can error our appropriately when the user attempts to perform a retryable write on the same transaction.

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: