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

New replication dep. on minvalid collection causes bad behavior

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Blocker - P1 Blocker - P1
    • 2.4.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:

      With the new behavior of using minvalid to determine if a initial sync has been done, and regular replication should start, leads to some significant problems.


      • Upgrade a set without minvalid collectoin: all nodes going into startup2(forever) if no primary/secondary is up, otherwise all nodes drop+resync all data.
      • Variations of this will cause the initial sync to fail/elect a primary because of the oplog stale rules
      • Removing the minvalid collection causes a full resync (ind. of data/indexes), or host going offline in startup2 until one can be done

      The upgrade case is bad since we had no need for the minvalid collection and it was not maintained nor guaranteed (esp. on the primary) or if replicas were seeded with a copy of the files without it.

            milkie@mongodb.com Eric Milkie
            scotthernandez Scott Hernandez (Inactive)
            0 Vote for this issue
            7 Start watching this issue