[SERVER-5052] mongos should read from the nearest config server, not the first one specified in the --configdb list Created: 23/Feb/12 Updated: 15/Aug/12 Resolved: 23/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kyle Banker | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
A mongos will read from the first config server specified in the --configdb argument. We should instead follow the same algorithm used to read from replica set secondaries, i.e., pick the a random node from the smallest ping bucket. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 23/Feb/12 ] |
|
This is by design, and until the config server system changes will remain in place. |