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

    XMLWordPrintable

    Details

    • Operating System:
      ALL
    • Backport Requested:
      v4.4, v4.2
    • Epic Link:
    • Sprint:
      Sharding 2020-11-02, Sharding 2020-11-16, Sharding 2020-11-30, Sharding 2020-12-14, Sharding 2020-12-28, Sharding 2021-01-11

      Description

      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

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-50144 Removing a shard with in-progress migration coordinators can leave permanently pending config.rangeDeletions document on recipient

          • Major - P3 - Major loss of function.
          • Open

            Activity

              People

              Assignee:
              backlog-server-sharding Backlog - Sharding Team
              Reporter:
              matthew.saltz Matthew Saltz
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated: