[SERVER-37129] Remove oldestOplogEntryTS invariants when we allow txns larger than 16MB Created: 13/Sep/18  Updated: 06/Dec/22  Resolved: 10/Apr/19

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

Type: Task Priority: Major - P3
Reporter: Pavithra Vetriselvan Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-40018 Remove ServerTransactionsMetrics::get... Closed
Assigned Teams:
Replication
Participants:

 Description   

Currently, we only write down oplog entries for in progress transactions if they are prepared. We have a few invariants in transaction_participant.cpp that make sure we do not set the oldest oplog entry timestamp if the transaction is not prepared.

This behavior changes once we allow multiple oplog entries per transaction, so we should remove those invariants for PM-1035.



 Comments   
Comment by Siyuan Zhou [ 10/Apr/19 ]

Thanks judah.schvimer. Closed this as a dup.

Comment by Judah Schvimer [ 10/Apr/19 ]

SGTM. samy.lanka, please make sure that all TODOs against this ticket are complete as part of SERVER-40018.

Comment by Siyuan Zhou [ 10/Apr/19 ]

pavithra.vetriselvan and samy.lanka, since we removed oldestOplogEntryOpTime entirely in SERVER-40018, shall we close this one as a dup to SERVER-40018? CC judah.schvimer.

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