[SERVER-1226] Reconstruction of config server metadata Created: 12/Jun/10  Updated: 04/Jul/10  Resolved: 12/Jun/10

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

Type: New Feature Priority: Major - P3
Reporter: Alex Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

There should be a section in DOCS explaining on how to reconstruct the metadata of the config servers.

If one looses all config servers it should be possible to reconstruct the metadata / config servers since the shards themselves know which chunks they hold. This is probably a pretty trivial task but it is not documented.
It probably could even be automated in a command like repairdb.

If one looses one out of three config servers it should be documented if one just needs to rsync the data of the healthy config servers to a new 3rd one or if any other actions need to be taken so that metadata can recover from readonly mode.
This could probably also be automated in a simple repair command.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 12/Jun/10 ]

Actually the opposite is true.
If every node goes down, the shards do in fact NOT know who is the owner of a given chunk.
This is why you need multiple config servers and they are all 2 phase commits.

Generated at Thu Feb 08 02:56:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.