-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Cluster Scalability
-
ALL
The client's recovery token will contain the shard name of a shard that's no longer in the cluster. I would expect the client's commitTransaction retry against mongos would return ShardNotFound.
This affects every release since 4.2.
One potential fix is for mongos to try to recover the transaction's outcome from all remaining shards. Chunk migration would need to transfer information about committed transactions.
- related to
-
SERVER-50143 Removing a shard with in-progress transaction coordinators can leave transactions on participants permanently in prepare
- Backlog