Loading...

XML

Word

Printable

JSON

Details

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.1, 4.7.0, 4.2.10
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.4, v4.2
Sprint:
Repl 2020-05-18, Repl 2020-06-01, Repl 2020-08-10
Linked BF Score:
26

Description

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.

Attachments

Issue Links

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

Activity

People

Assignee:: Tess Avitabile (Inactive)

Reporter:: Matthew Russotto

Participants:: Githook User, Matthew Russotto, Tess Avitabile

Votes:: 0 Vote for this issue

Watchers:: 11 Start watching this issue

Dates

Created:: Apr 17 2020 10:02:29 PM UTC

Updated:: Oct 29 2023 10:09:17 PM UTC

Resolved:: Jul 29 2020 05:29:57 PM UTC