[SERVER-18330] mongos fails to start Created: 05/May/15 Updated: 06/Apr/23 Resolved: 05/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.1.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Alexandru Toth | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Major Change |
| Operating System: | ALL |
| Steps To Reproduce: | download and install latest mongoDB server create 2 shards as instructed and restore the database try to lunch a mongos |
| Participants: |
| Description |
|
Hello I have reproduced the situation from Q8-Q10 from the mongoDB exam 102. Test environment: created the config server and the shards. I am able to logon to config server like this: mongo localhost:27091/config. It takes me straight to the database that was restored. config server was restarted. when I type mongos --configfb localhost:27091 --port 28000 it fails with the following message: BadValue Must have either 3 node old-style config servers, or a single server re |
| Comments |
| Comment by Kaloian Manassiev [ 05/May/15 ] |
|
Hi Alexandru, Thank you for bringing this to our attention. As of version 3.1 of the product, we have intentionally removed the ability to use a standalone mongod instance as the config server. This is in order to make the role of a config server explicit and to ease the transition to using replica sets as config servers. The course text will have to be fixed and I will file a separate bug for this. In the mean time, please note that server versions prior to 3.1 (i.e., 3.0 and 2.6) still support running a single-node config server. Best regards, |