[SERVER-50143] Removing a shard with in-progress transaction coordinators can leave transactions on participants permanently in prepare Created: 06/Aug/20  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: ShardedTxn:KnownBugs, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-50144 Removing a shard with in-progress mig... Backlog
is related to SERVER-55228 Client will not be able to use transa... Backlog
Assigned Teams:
Cluster Scalability
Operating System: ALL
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
Participants:

 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

Generated at Thu Feb 08 05:21:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.