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

Make update_in_transaction_states.js' initUpdateInTransactionStates target update by shard key

    • Cluster Scalability
    • Fully Compatible
    • v8.0
    • 0

      initUpdateInTransactionStates performs an updateOne by _id, where _id is not necessarily the shard key. This is known to produce incorrect results in presence of concurrent chunk migrations. While PM-3190 aims to fix this, this can cause test failures in older branches, and also when the feature flag is off. Moreover, it looks like PM-3190 has been rescoped to not fix this when retryableWrites are not used.

      The test can be fixed by targeting the updateOne by shard key skey instead of by _id.

            Assignee:
            abdul.qadeer@mongodb.com Abdul Qadeer
            Reporter:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: