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

Ignore some NoProgressMade errors in sharding_balance4.js

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.5.5
    • 3.4.4, 3.5.6
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • v3.4
    • Sharding 2017-04-17
    • 0

    Description

      The sharding_balance4.js test fails occasionally because more than 5 migrations manage to complete since the write operation started and because of this the write never manages to establish a shard version.

      We should ignore up to certain number of NoProgressMade errors in order to make the test less likely to fail. This doesn't fix the inherent raciness though.

      Attachments

        Activity

          People

            kaloian.manassiev@mongodb.com Kaloian Manassiev
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: