-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.4, v4.2
-
Repl 2020-05-18, Repl 2020-06-01, Repl 2020-08-10
-
26
If we abort a transaction on a primary, we may never have written anything durably about it. If we step down, we must forget about all aspects of this transaction, including the transaction number (which may be re-used on the new primary). This means we must not just abort transactions in progress, but also invalidate all sessions, on stepdown.
We should also invariant in beginOrContinueTransactionUnconditionally, when we are attempting to start the same transaction number as already exists on the participant, but that transaction number is not in progress.
- depends on
-
SERVER-48641 Deadlock due to the MigrationDestinationManager waiting for write concern with the session checked-out
- Closed
-
SERVER-48689 MigrationDestinationManager waits for thread to join with session checked out
- Closed
- related to
-
SERVER-49044 Make AsyncRequestSender not retry remote command requests with startTransaction=true
- Closed
-
SERVER-88289 Remove manual check that skips retrying requests with startTransaction in ARS
- Backlog