[SERVER-36483] Transaction reaper should not reap 'config.transactions' entries for sessions with prepared transactions Created: 07/Aug/18  Updated: 29/Oct/23  Resolved: 02/May/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.11

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: prepare_errors
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-37348 TransactionReaper and periodic transa... Closed
Duplicate
is duplicated by SERVER-38576 Ban direct writes to transaction tabl... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-08-27, Sharding 2019-02-25, Sharding 2019-03-11, Sharding 2019-03-25, Sharding 2019-04-08, Sharding 2019-04-22, Sharding 2019-05-06
Participants:

 Comments   
Comment by Githook User [ 02/May/19 ]

Author:

{'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}

Message: SERVER-36483 Do not reap transaction entries for prepared transactions
Branch: master
https://github.com/mongodb/mongo/commit/dcf7912e275b72d1462d4ecf26f195f8accb45ad

Comment by Judah Schvimer [ 04/Sep/18 ]

I updated the summary to clarify.

Comment by Esha Maharishi (Inactive) [ 04/Sep/18 ]

judah.schvimer, if the ticket is saying the TransactionReaper should not reap entries with prepared transactions fromĀ config.transactions, then that is still work that needs to be done (unless it's been done already and I'm not aware of it).

(On the other hand, we do not need to prevent the TTL index on the config.system.sessions collection from reaping session records in config.system.sessions, even if the corresponding entry for the session in config.transactions is a prepared transaction).

Comment by Judah Schvimer [ 04/Sep/18 ]

I think this was referring to the TransactionReaper actually. Is that still "Works as Designed" esha.maharishi, or is that work that still needs to be done?

Comment by Esha Maharishi (Inactive) [ 23/Aug/18 ]

I think this can be closed as "Works as Designed" - just clarified with Jason Carey the relationship between the sessions collection and transactions collection.

It is ok if the transaction collection has an entry for a session, but the sessions collection doesn't.

Comment by Gregory McKeon (Inactive) [ 23/Aug/18 ]

esha.maharishi and pavithra.vetriselvan should sync up when the design for the transaction reaper settles.

Generated at Thu Feb 08 04:43:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.