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

Client will not be able to use transaction recovery token to retry commitTransaction if recovery shard gets removed

    • Cluster Scalability
    • ALL

      The client's recovery token will contain the shard name of a shard that's no longer in the cluster. I would expect the client's commitTransaction retry against mongos would return ShardNotFound.

      This affects every release since 4.2.

      One potential fix is for mongos to try to recover the transaction's outcome from all remaining shards. Chunk migration would need to transfer information about committed transactions.

        1. no-repro-when-transition-to-dedicated-configsvr.js
          2 kB
          Jordi Serra Torrens
        2. repro-server-55228.js
          2 kB
          Jordi Serra Torrens

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: