Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.1.9
Affects Version/s: None
Component/s: Replication
Labels:
- prepare_errors

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25, Sharding 2019-03-11

Periodic transaction killer kills unprepared transactions that run longer than 60 seconds. It shouldn't kill transactions on secondaries. Currently, it's very unlikely to have transactions in "kInProgress" state longer than 60 seconds on secondaries since such transactions become prepared right after applying all their write operations; this will be more likely when we start to support transactions consisting of multiple oplog entries.

Session reaper and other periodic threads may have the same issue and need auditing.

depends on

SERVER-36483 Transaction reaper should not reap 'config.transactions' entries for sessions with prepared transactions

Closed

SERVER-36485 ‘killSessions’ (for one session) and 'endSessions' should return a “PreparedTransactionInProgress” error if it tries to kill a session that has a prepared transaction in it

Closed

is depended on by

SERVER-38297 Killing session on a secondary currently applying prepare oplog entry can fassert

Closed

SERVER-38876 Ensure secondary user operations cannot abort transactions being applied from the oplog

Closed

related to

SERVER-38297 Killing session on a secondary currently applying prepare oplog entry can fassert

Closed

SERVER-40487 Stop running the RstlKillOpthread when a node is no longer primary

Backlog

(1 related to)

Assignee:: Matthew Saltz (Inactive)

Reporter:: Siyuan Zhou

Participants:: Githook User, Judah Schvimer, Matthew Saltz, Siyuan Zhou

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Created:: Sep 27 2018 03:46:53 PM UTC

Updated:: Oct 29 2023 10:27:52 PM UTC

Resolved:: Feb 25 2019 11:03:12 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates