[SERVER-5630] mongos unable to start give error "differconfig servers not in sync! config servers ". Created: 17/Apr/12 Updated: 26/Sep/16 Resolved: 01/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.0.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | jitendra | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
oracle linux |
||
| Issue Links: |
|
||||||||||||||||
| Operating System: | Linux | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
hi, we setup mongo servers on two machine. All mongod run with journal option. machine_1 : 4 mongod, 2 config server, 1 mongos. I reboot machine_1. start all mongods and config server after this start mongos.
Tue Apr 17 18:49:17 /usr/local/ct/depend/mongo/bin/mongos db version v2.0.3-rc0, pdfile version 4.5 starting (--help for usage) kindly help me how to start mongos. Thanks in advance |
| Comments |
| Comment by Jean Nascimento [ 07/Jan/13 ] |
|
Worked, thanks for the tip! |
| Comment by Spencer Brody (Inactive) [ 23/Apr/12 ] |
|
We generally don't recommend automating any change that involves messing with config data, as that is very risky and if done incorrectly can leave your cluster unusable (if the config data gets messed up the mongoses won't know where to route requests for data). It should be very rare for your config servers to get out of sync. We are planning to create scripts to make this process easier in the future ( That said, every step of the process I outlined above should be possible to script fairly easily - just be sure to test any such script thoroughly and use at your own risk. |
| Comment by jitendra [ 22/Apr/12 ] |
|
hi Thanks in advance |
| Comment by Spencer Brody (Inactive) [ 17/Apr/12 ] |
|
It looks like your config servers got out of sync. There was probably a migration or chunk split in progress when you shut down the machine. Your best bet is to connect to each of the config servers directly and query the changelog collection in the config database to find which of them has the entry with the latest timestamp. Once you identify which config server has the most up-to-date copy of the data you should restore its data onto the other 2 config servers. Once the servers are brought back into sync, the mongos should be able to start up properly. |