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

Declaring bind_ip in conf file makes arbiter fail in a nasty way

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.5
    • Component/s: Replication
    • None
    • ALL
    • Hide

      1. Create a replica set with 2 normal members and a arbiter without declaring bind_ip in conf file
      2. Declare bind_ip in arbiter conf file
      3. Restart arbiter.
      Bob is your uncle....

      Show
      1. Create a replica set with 2 normal members and a arbiter without declaring bind_ip in conf file 2. Declare bind_ip in arbiter conf file 3. Restart arbiter. Bob is your uncle....

      Begining with Mongo 3.2.5 all instances in a replica set starts with:

        • WARNING: The server was started without specifying a --bind_ip and listens for connections on all available network interfaces.

      We have replica sets with 2 normal members and a arbiter
      If I add the bind_ip to a working replica set and restart the arbiter it joins the replica set with "Our replica set configuration is invalid or does not include us". If both other members of the replica set is restarted they both join in secondary state

        1. mongoarb.1.conf
          0.6 kB
        2. mongoarb.1.with_bind_ip.log
          285 kB
        3. mongoarb.1.without_bind_ip.log
          5 kB

            Assignee:
            Unassigned Unassigned
            Reporter:
            myMarck Nicolai Marck Ødum [X]
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: