ReplicaSet configuration info differs among members after dropping & adding members

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.0.0
    • Component/s: Replication
    • None
    • Windows
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I setup a MongoDB replicaset.

      At the beggining, due to limited hardware, I created three MongoDB instances in one server and different ports, then add the three instances into one replicaset.

      Subsequently, I got an arbiter server, so I added the arbiter into the replicaset and then dropped one instance.

      Lastly, I got another server which I configured as a normal MongoDB data instance, so I added it into the replicaset and dropped another instance sitting on the first server from the replicaset.

      Now, I realise I have good replicaset config information in both data node, but not the arbiter server. The arbiter server is still showing the very first replicaset config in which members 3 instance in one same server.

      I tried various ways to change the replicaset config information in the arbiter server but all in vain. How do I fix this?

            Assignee:
            Unassigned
            Reporter:
            Yang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: