[SERVER-13694] Config server consistency check command Created: 23/Apr/14  Updated: 06/Dec/22  Resolved: 03/Jan/19

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

Type: Improvement Priority: Major - P3
Reporter: Jon Rangel (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   

It would be good to have a convenient and foolproof way to check the consistency of the config servers in a sharded cluster.

Currently, the only indication that config servers are out of sync is the following message in the logs:

[mongosMain] ERROR: config servers not in sync! config servers config1.example.net:27019 and config3.example.net:27019 differ

The dbHash command can be used to compare the contents of config servers, but requires careful interpretation as some collections are expected to differ between config servers whereas others must not.

A command that could be run from a mongos to check config server consistency would be a good thing. Additionally, this command should report whether config servers are in 'read-only' mode (due to inconsistency or a config server being down), to give users confidence that the cluster meta-data is not updatable during critical operations such as cluster backup or restoration of a config server.



 Comments   
Comment by Kaloian Manassiev [ 03/Jan/19 ]

This is no longer necessary now that we have CSRS.

Generated at Thu Feb 08 03:32:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.