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

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

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

      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.

            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            0 Vote for this issue
            2 Start watching this issue