[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: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 5 years, 4 weeks, 6 days ago | ||||||||
| Description |
Descriptionhttps://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:
Election term is value of t here:
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 changesImpact to Other DocsMVP (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 |