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

XMLWordPrintableJSON

    • Cluster Scalability
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Cluster Scalability
              Reporter:
              Esha Maharishi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: