ConfigureCollectionAutoSplit should check maxChunkSize in MB

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.3.0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding EMEA 2022-02-07
    • 175
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      TheĀ current check for max chunk size being within required bounds of 1MB to 1GB occurs after converting the max chunk size from the user to bytes from mb. This can cause an overflow without a proper error message if the user tries to input the max chunk size in bytes and ends up well beyond the limit of the command. We should check the bounds without the possibility of overflowing the int if the user input an invalid value.

            Assignee:
            Allison Easton
            Reporter:
            Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: