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

Clean shutdown should leave secondaries without the batch-in-progress flag

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.2.9
    • Replication
    • Fully Compatible
    • ALL
    • Repl 18 (08/05/16)

    Description

      This ensures that they can go directly to SECONDARY without needing to contact other nodes. This is an extension of SERVER-24933 which made shutdown only happen between batches but could leave the secondary in a state where it had to fetch and apply a batch before reaching SECONDARY state.

      This ticket is for the 3.2 work which is being done first. The forward-port to 3.4/master will be ticketed separately.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-25773 Upgrade from 3.0.9 to 3.2.9 discards oplog and can't catch up

          • Blocker - P1 - Blocks development and/or testing work, production could not run.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-24933 Clean shutdown of secondaries should occur in between oplog batches, not during

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

          Activity

            People

              mathias@mongodb.com Mathias Stearn
              mathias@mongodb.com Mathias Stearn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: