[SERVER-1538] isMaster fails for uninitiated replica set Created: 02/Aug/10 Updated: 12/Jul/16 Resolved: 02/Aug/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 1.5.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael Dirolf | Assignee: | Dwight Merriman |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
When running isMaster on an uninitiated rs I get: {u'info': u"can't currently get local.system.replset config from self or any seed (EMPTYUNREACHABLE)", u'ismaster': False, u'ok': 0.0, u'errmsg': u'replSet still trying to initialize'}The problem is that some drivers (PyMongo at least) run an isMaster command automatically on first connect to try to find the master/primary, ensure the connection is working, etc. So I can't connect to the set to run the initiate command from the driver. Any reason 'ok' can't be true/1.0 for this case? |
| Comments |
| Comment by auto [ 02/Aug/10 ] |
|
Author: {'login': 'mdirolf', 'name': 'Mike Dirolf', 'email': 'mike@10gen.com'}Message: start of a simple-setup script for replSets, based on mathias' for sharding. not working yet, waiting on |