Make tests that rely on the autosplitter unintentially not require the autosplitter

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.2
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2018-08-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Some tests like authCommands.js insert some documents and then call moveChunk, expecting the autosplitter to have run. With the new autosplitting behavior, splitting is asynchronous, so it won't necessarily have completed in between the inserts and the moveChunk, so the moveChunk will fail because the chunk will be too large. These tests are not intentionally testing this autosplitter behavior, so they shouldn't rely on it. In cases like these we should call the splitChunk command manually.

            Assignee:
            Matthew Saltz (Inactive)
            Reporter:
            Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: