-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Sharding 2019-01-14, Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25
If a user accidentally restores a cluster incorrectly or the server gets into a bad state, we need a way to explicitly abort a prepared transaction other than an 'abortTransaction' command from the coordinator. Preferably there would be a way to do this for all prepared transactions at once.
- is related to
-
TOOLS-2222 Mongodump should ignore config.transactions and config.transaction_coordinators
-
- Closed
-
-
SERVER-39699 Add a way for abortTransaction to be broadcast to all shards
-
- Closed
-
- related to
-
SERVER-38060 Don't run after test hooks in resmoke if the test fails
-
- Closed
-
- links to