-
Type:
Bug
-
Status: Open
-
Priority:
Major - P3
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 5.0 Required, 4.4 Required, 4.2 Required
-
Component/s: Sharding
-
Labels:
-
Operating System:ALL
-
Backport Requested:v4.4, v4.2
-
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
The following scenario can occur:
- Transaction coordinator on shard X makes a commit/abort decision after hearing from all participants
- Shard X is removed and shut down before transaction coordinator sends decision to participant shards
- Participant shards are stuck permanently with prepared transactions
- is related to
-
SERVER-50144 Removing a shard with in-progress migration coordinators can leave permanently pending config.rangeDeletions document on recipient
-
- Open
-