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

Require 'force' argument to stepdown or shutdown a node in a single-node replica set

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • 2.8.0-rc1
    • 2.8.0-rc1
    • Replication
    • None
    • Minor Change
    • ALL

    Description

      In a multi-node replica set you need the 'force' argument to stepdown or shutdown a primary if doing so would leave the system without a usable primary, a single-node should be no different.

      Attachments

        Issue Links

          is documented by

          Improvement - An improvement or enhancement to an existing feature or task. DOCS-4349 Document changes to shutdown/stepdown in replication

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-43988 shutdown ({force:false}) should refuse to shut down if there is an index build in progress

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-3695 Running shutdown command on Primary while all secondaries are fsync locked and not caught up says that no secondaries were within 10 seconds of primaries optime, even if they were

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              spencer@mongodb.com Spencer Brody (Inactive)
              spencer@mongodb.com Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: