Uploaded image for project: 'Core Server'
  1. Core Server
  2. 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

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor - P4
    • Resolution: Works as Designed
    • 2.0.0-rc0
    • None
    • Replication, Usability

    Description

      If you try to run the shutdownServer command on a primary, it won't step down unless there is a secondary totally caught up. The error message it reports, however, is "shutdownServer failed: no secondaries within 10 seconds of my optime". Either the error message should be updated or the behavior should be changed to match the message.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-16377 Require 'force' argument to stepdown or shutdown a node in a single-node replica set

          • 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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: