[SERVER-82731] Document restore procedure updates for co-located configrs / queryable Created: 02/Nov/23  Updated: 09/Nov/23  Resolved: 09/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Peter Vertenten Assignee: Jack Mulrow
Resolution: Community Answered Votes: 0
Labels: sharding-nyc-subteam2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding NYC
Participants:

 Description   

This is the general restore procedure not serverless. Would need to know if there are changes for queryable restores as well.

https://docs.google.com/document/d/16DGt-RsiN9l3oStcjJeJ0iWIVk2je1Xt6L_cDYp6rTw/edit#heading=h.xzu4vp4udw13



 Comments   
Comment by Peter Vertenten [ 09/Nov/23 ]

Thanks thats great. Will watch PM-3244.

Comment by Jack Mulrow [ 09/Nov/23 ]

That should be everything for regular restores with a colocated config server, but IIRC queryable restores require "queryable backup mode" which config servers won't support until https://jira.mongodb.org/browse/PM-3244.

As for tests - I updated the existing servers tests in this commit for SERVER-76318.

Comment by Peter Vertenten [ 06/Nov/23 ]

If that is the totality great.

Anything different needed for queryable restores?

Are there automated tests testing the recovery with colocated configrs that cloud engineers can reference?

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