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

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Cluster Scalability
    • ALL
    • v8.0
    • 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

        1. 0001-No-repro-when-transitioning-to-dedicated-config-serv.patch
          7 kB
        2. 0001-Repro-SERVER-50143.patch
          6 kB

            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:
            10 Start watching this issue

              Created:
              Updated: