Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
3.5.13
-
None
-
None
-
Minor Change
-
ALL
-
Sharding 2017-10-23, Sharding 2017-11-13
-
0
Description
The TransactionReaper mistakenly uses the time component of lastWriteOpTimeTs to notice transaction records over N minutes old (which we use to decide when transaction records are eligible for deletion due to a lack of a session record).
We should flush an additional field to the transaction table which includes a wall clock time to compare against, as well as a redirecting the reaper to use that field for eligibility.
Attachments
Issue Links
- depends on
-
SERVER-31678 Thread through the operation wall-clock time for oplog entries
-
- Closed
-
- related to
-
SERVER-32159 fix typo in sync_tail.cpp fillWriterVectorsAndLastestSessionRecords()
-
- Closed
-