Get rid of `maxSize` for shards

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • Sharding EMEA 2022-08-08, Sharding EMEA 2022-08-22, Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19
    • 44
    • 1.5
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Get rid of maxSize since it's a soft constraint and doesn't even do well what it's intended to do: it's a legacy parameter that made sense with the MMAP storage engine. Nowadays, the WT storage engine stores data in compressed form so this parameter is not honored anymore.

      Behavioral changes and upgrade/downgrade considerations:

      • In versions >= 6.1 if you specify maxSize on addShard we will error with “InvalidOptions”
      • maxSize configuration field in config.settings will be kept until 7.0 to support dowgrade and then removed completely as part of 7.1 FCV upgrade procedure (SERVER-68430)

            Assignee:
            Enrico Golfieri
            Reporter:
            Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: