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

Removing a shard with in-progress transaction coordinators can leave transactions on participants permanently in prepare

XMLWordPrintableJSON

    • Cluster Scalability
    • ALL
    • Sharding 2020-11-02, Sharding 2020-11-16, Sharding 2020-11-30, Sharding 2020-12-14, Sharding 2020-12-28, Sharding 2021-01-11

      The following scenario can occur:

      1. Transaction coordinator on shard X makes a commit/abort decision after hearing from all participants
      2. Shard X is removed and shut down before transaction coordinator sends decision to participant shards
      3. Participant shards are stuck permanently with prepared transactions

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: