-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
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
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)
- causes
-
SERVER-84187 Regression in balancer round storage statistics retrieval
-
- Blocked
-
- is depended on by
-
COMPASS-6095 Investigate changes in SERVER-66297: Get rid of `maxSize` for shards
-
- Closed
-
- is documented by
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
SERVER-2246 Pay (more) attention to sharding maxSize
-
- Closed
-
- related to
-
-
- Closed
-