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

Can't failover last SECONDARY node with Replica set.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Works as Designed
    • None
    • None
    • None
    • None
    • ALL
    • Hide

      create a 3 member replica set.
      knock one out.
      watch them failover fine. cool.
      knock another out
      watch the your db go offline.

      Show
      create a 3 member replica set. knock one out. watch them failover fine. cool. knock another out watch the your db go offline.

    Description

      this is a dupe of SERVER-2826. I think it is absolute bullshit that a replica set can't survive if all but one dies.

      Give us a way to instruct a member to be primary without a majority. Let us be the arbiter.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-2826 Can't failover last SECONDARY node with Replica set.

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. DOCS-1290 Create docs page explaining *why* we require a majority of the set to be up to have a PRIMARY

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              nicholas.tang@mongodb.com Nicholas Tang
              optimuspaul Paul DeCoursey
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: