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

migrations should use better slave count to determine up-to-date

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 2.0.3, 2.1.0
    • 2.2.5, 2.4.5, 2.5.1
    • Replication, Sharding
    • None
    • ALL

    Description

      ... currently we're using a count that is never actually flushed out, except on reconfig (in 2.1, potentially in 2.0).

      Also we may want to rethink our logic of waiting until the majority of slaves (# slaves / 2 + 1) is caught up. Why not majority of the set, for example?

      Attachments

        Issue Links

          Activity

            People

              randolph@mongodb.com Randolph Tan
              greg_10gen Greg Studer
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: