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

Prevent users from specifying a lower max than min bound in merge chunks command

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2023-11-13, CAR Team 2023-11-27
    • 5
    • 1

      In BF-30376, we saw that the collection_defragmentation test could, in very rare occasions, send a merge chunks command where the min bound was greater than the max bound. This wouldn't be a problem in production because this range wouldn't pass the checks we have that the range to be merged matches existing chunks.
      However, in tests, this causes a dassert to fail when we create a chunk range out of these bounds values.

      This can be fixed simply by checking in the shardsvrMergeChunks command if the max bound is less than the min bound, and throwing an error if so.

            robert.sander@mongodb.com Robert Sander
            allison.easton@mongodb.com Allison Easton
            0 Vote for this issue
            3 Start watching this issue