[SERVER-2613] Store config server data in accessible, redundant collection in mongos itself for disaster recovery Created: 23/Feb/11 Updated: 16/Jan/24 Resolved: 16/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Kyle Banker | Assignee: | Matt Panton |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | RachitaD | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Participants: |
| Description |
|
There have been a number of situations where users have entirely lost their config data (usually because they're running just one config server). It might be useful to store an easily accessible copy of the config database in each mongos. As long as they still have a single mongos online, the recovery of the data could be greatly simplified. |
| Comments |
| Comment by Matt Panton [ 16/Jan/24 ] |
|
Starting in MongoDB 3.4 a Config Server must be a Replica Set, ensuring high availability for config data. |
| Comment by Eliot Horowitz (Inactive) [ 23/Feb/11 ] |
|
Would be easy to add a command to write config to a new server. |