Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-1538

isMaster fails for uninitiated replica set

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5.8
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL

      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?

        Attachments

          Activity

            People

            Assignee:
            dwight_10gen Dwight Merriman
            Reporter:
            mike Michael Dirolf
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: