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

Removing a node from a replica set can't succeed when one node is syncing

XMLWordPrintableJSON

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

      Have a working replica set.
      Add a new node.
      Before the new node syncs (goes past STARTUP2) rs.remove() any node of the working replica set nodes.

      Show
      Have a working replica set. Add a new node. Before the new node syncs (goes past STARTUP2) rs.remove() any node of the working replica set nodes.

      Given I have a replica set with a number of nodes (>3) and one of them is syncing (in STARTUP2). As soon as I remove a node (be it SECONDARY or the PRIMARY) there will be a PRIMARY reelection, which appears to wait for the one node to finish the startup (in fact this node wants to become a primary). This however is never going to succeed, because no primary will be elected.

      Maybe rs.remove() should give an error in such a case.

            Assignee:
            matt.dannenberg Matt Dannenberg
            Reporter:
            reezer Christian Sturm
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: