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

state transition for replica sets isn't correct

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 2.2.0
    • 2.2.1
    • Replication
    • None
    • ALL

    Description

      A node that is initial syncing is in state STARTUP2. If all goes well, it transitions to state SECONDARY, then RECOVERING, then back to SECONDARY. The first SECONDARY state is a mistake; it should go straight to RECOVERING.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-7186 Batched oplog application increases frequency of idempotency violations

          • 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-3251 Overflowed replica set members briefly re-initialize as SECONDARY

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

          Activity

            People

              kristina Kristina Chodorow (Inactive)
              milkie@mongodb.com Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: