[SERVER-52624] Cache the pointer to the oplog collection before running recoverToOplogTimestamp Created: 04/Nov/20  Updated: 29/Oct/23  Resolved: 06/Nov/20

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

Type: Bug Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-52617 Cache the pointer to the oplog collec... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-11-16
Participants:

 Description   

Same as SERVER-52617 but for master branch



 Comments   
Comment by Githook User [ 06/Nov/20 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-52624: Remove useless setOplogCollectionName and getOplogCollectionName from LocalOplogInfo
Branch: master
https://github.com/mongodb/mongo/commit/ca3c18008bff68e2684ad5954452c6513f7a744e

Comment by Githook User [ 06/Nov/20 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-52624: Cache the pointer to the oplog collection before running recoverToOplogTimestamp
Branch: master
https://github.com/mongodb/mongo/commit/a53936d6b01f26babe3ac2be79be68e8334590b2

Comment by Lingzhi Deng [ 04/Nov/20 ]

We should also investigate whether we can clean up the logic in LocalOplogInfo::setOplogCollectionName to always use NamespaceString::kRsOplogNamespace.

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