[SERVER-42965] Unused parameter "stableTimestampForRecovery" Created: 22/Aug/19  Updated: 29/Oct/23  Resolved: 22/Aug/19

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

Type: Improvement Priority: Minor - P4
Reporter: A. Jesse Jiryu Davis Assignee: A. Jesse Jiryu Davis
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-08-26
Participants:

 Description   

This value is in OplogApplier::Options and it's a parameter to SyncTail::syncApply and all the lambdas in kOpsMap. According to the comment in OplogApplier, "For replication recovery only. During replication rollback, this is used to keep track of the stable timestamp from which we replay the oplog." After the Oplog Durability project, however, this parameter is unused.

As pavithra.vetriselvan says, "This is no longer needed after the oplog durability project because we do not need to compare the commitTimestamp to the stableTimestamp. This was originally used to tell whether prepared operations were already reflected in the data."



 Comments   
Comment by Githook User [ 22/Aug/19 ]

Author:

{'username': 'ajdavis', 'email': 'jesse@mongodb.com', 'name': 'A. Jesse Jiryu Davis'}

Message: SERVER-42965 Remove unused param "stableTimestampForRecovery"
Branch: master
https://github.com/mongodb/mongo/commit/2e0eb6286f37a132e32d4a42dc5680229e2587f2

Generated at Thu Feb 08 05:01:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.