[SERVER-21149] Cannot start mongos with --configdb pointing to a replset connection string that doesn't include the CSRS primary Created: 26/Oct/15 Updated: 25/Jan/17 Resolved: 29/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding B (10/30/15), Sharding C (11/20/15) |
| Participants: |
| Description |
|
While trying to auto-discover the rest of the config replset, the ReplicaSetMonitor will run isMaster commands against the nodes discovered by the seed list of the config server replset, but establishing connections to those auto-discovered nodes will fail because they aren't yet present in the ShardRegistry. |
| Comments |
| Comment by Githook User [ 29/Oct/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |