Resharding txn cloner can miss config.transactions entry when fetching

XMLWordPrintableJSON

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

      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.

              Assignee:
              Randolph Tan
              Reporter:
              Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: