[SERVER-14291] resolving config database coruption situation Created: 18/Jun/14  Updated: 10/Dec/14  Resolved: 18/Jun/14

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

Type: Question Priority: Major - P3
Reporter: Ofer Shani Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

We have experienced the case when the config database on each of the 3 config servers become different (their hash value differs).

While having all three servers out of sync, how do I choose the right one to restore the rest of the config servers from.



 Comments   
Comment by Thomas Rueckstiess [ 18/Jun/14 ]

Hi Ofer,

The SERVER project is for reporting bugs or feature suggestions for the MongoDB server.

For MongoDB-related support discussion please post on the mongodb-users group (http://groups.google.com/group/mongodb-user) or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group.

Also please note that we expect some of the collections to have different dbHashes across the config servers, namely the ones that use timestamps (e.g. config.lockpings). We only compare a subset of collections in terms of their dbHashes (config.databases, config.collections, config.chunks, config.settings). If the hashes for one (or several) of these collections are different, you'd have to look at the actual metadata and see what the differences are. There is no good general answer which one of the config servers to pick without considering recent events and looking at the actual differences.

Regards,
Thomas

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