[DOCS-12347] Missing step to remove minOpTimeRecovery document during shared cluster restore Created: 10/Jan/19  Updated: 10/Jan/19  Resolved: 10/Jan/19

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Eric Sommer Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates DOCS-12315 Update restore procedure Closed
Participants:
Days since reply: 5 years, 4 weeks, 6 days ago

 Description   

Description

https://docs.mongodb.com/manual/tutorial/restore-sharded-cluster/

Prior to this step on the shards, this step is missing:

Remove the

{"_id": "minOpTimeRecovery"}

from the admin.system.version collection

That document contains the minimum timestamp and election term for inclusion in queries to the CSRS. If the original cluster's CSRS experienced elections, the election term will be > 1 in that document. For example:

{ "_id" : "minOpTimeRecovery", "configsvrConnectionString" : "configRepl/localhost:39008,localhost:39009,localhost:39010", "minOpTime" : { "ts" : Timestamp(1547112229, 5), "t" : NumberLong(2) }, "minOpTimeUpdaters" : 0, "shardName" : "shard01" }

Election term is value of t here:

"t" : NumberLong(2) 

Meanwhile, the newly restored CSRS will start out with election term = 1. If the document is not removed and the term > 1 in that document, it will result in unsatisfiable queries to the CSRS (since the CSRS term will never match the query term). This leaves the restored cluster in a degraded state.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Ravind Kumar (Inactive) [ 10/Jan/19 ]

Thanks for filing this eric.sommer.

 

This looks like a duplicate of DOCS-12315, which is on deck for this week. I'll link this ticket for reference as part of the work on that and bump the priority.

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