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

Resharding txn cloner can miss config.transactions entry when fetching

    • Fully Compatible
    • ALL
    • Sharding 2021-03-22, Sharding 2021-04-05, Sharding 2021-04-19
    • 42
    • 2

      This is because we use readConcern snapshot + atClusterTime and readPref nearest.

      The issue is that, in secondaries, we squash multiple updates to config.transactions into one and use the newest timestamp when calling setTimestamp. So if we have 3 writes from retryable that corresponds to ts1, ts2 & ts3, the secondary will only have ts3 set properly and you will not be able to see the config.transactions document when reading with atClusterTime ts1 or ts2.

        1. test.js
          2 kB
          Randolph Tan

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

              Created:
              Updated:
              Resolved: