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

Ignore some NoProgressMade errors in sharding_balance4.js

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.5.5
    • Fix Version/s: 3.4.4, 3.5.6
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4
    • Sprint:
      Sharding 2017-04-17
    • Linked BF Score:
      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

            Assignee:
            kaloian.manassiev Kaloian Manassiev
            Reporter:
            kaloian.manassiev Kaloian Manassiev
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: