[SERVER-44442] Allow queryableBackupMode to perform replication recovery Created: 05/Nov/19  Updated: 29/Oct/23  Resolved: 06/Jan/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.2.4, 4.3.3

Type: New Feature Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-55421 Relax index constraints when recoverT... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2
Sprint: Execution Team 2019-12-16, Execution Team 2019-12-30, Execution Team 2020-01-13, Execution Team 2019-12-30
Participants:

 Description   

Introduce a new server parameter recoverToOplogTimestamp. This parameter will only have replication recovery play to up to and including that oplog entry (if it exists). Format: --setParameter "recoverToOplogTimestamp={timestamp: Timestamp(1565014064, 13)}"

When --queryableBackupMode is supplied on startup along with the new recoverToOplogTimestamp server parameter, the server should perform replication recovery. I.e: The server should only turn on read-only mode after storage engine startup and after replication recovery completes. This should end up similar to recoverFromOplogAsStandalone.



 Comments   
Comment by Githook User [ 11/Feb/20 ]

Author:

{'username': 'GWlodarek', 'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com'}

Message: SERVER-44442 Allow queryableBackupMode to perform replication recovery

(cherry picked from commit d8c8abbbbc716b431ac33ef768a4f71644eda75d)
Branch: v4.2
https://github.com/mongodb/mongo/commit/e25bda29e897881a864e4721174ff5f3a4f33efe

Comment by Githook User [ 06/Jan/20 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-44442 Allow queryableBackupMode to perform replication recovery
Branch: master
https://github.com/mongodb/mongo/commit/d8c8abbbbc716b431ac33ef768a4f71644eda75d

Comment by Gregory Wlodarek [ 06/Jan/20 ]

We've made a minor change to the --setParameter to avoid creating a new parser.

The new format is: --setParameter "recoverToOplogTimestamp={timestamp: Timestamp(1565014064, 13)}"

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