[DOCS-7082] Config server upgrade requires "in sync" but doesn't say how Created: 03/Feb/16  Updated: 30/Oct/23  Resolved: 01/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Andrew Ryder (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769

 Description   

RE: https://docs.mongodb.org/manual/tutorial/upgrade-config-servers-to-replica-set/#prerequisites

The existing config servers must be in sync.

But how does one check?

Traditionally (or internally here in support land), we've used the dbHash command run against each config server directly and then we just sort of "know" which collections to verify. The 'databases', 'collections', 'chunks', 'tags', 'shards' and 'version' collections need to match in the results (all others can be ignored).

Can we document / recommend a method for checking consistency between 3 config servers?

EDIT: fixed the list of collections we usually check for



 Comments   
Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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