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

Remove usage of toArray in collection_defragmentation.js

    • Fully Compatible
    • ALL
    • v6.0
    • Hide

      Setting numChunks to >130 and running in concurrency_sharded_with_stepdowns_and_balancer ensures this failure happens pretty regularly

      Show
      Setting numChunks to >130 and running in concurrency_sharded_with_stepdowns_and_balancer ensures this failure happens pretty regularly
    • Sharding EMEA 2022-06-13
    • 29

      The mergeChunks state of collection_defragmentation.js gets all chunks from config.collections using toArray. If there are a lot of chunks (usually >100 needed) this can require a call to getMore which will fail if the test is being run on a suite that involves stepdowns (concurrency_sharded_with_stepdowns_and_balancer, concurrency_sharded_kill_primary_with_balancer, etc.).

      In order to allow the test to continue running on these suites, we should remove the call to toArray and simply check a random subset of the chunks for mergeability in each mergeChunks phase so that getMore is not called.

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: