[COMPASS-6095] Investigate changes in SERVER-66297: Get rid of `maxSize` for shards Created: 02/Sep/22  Updated: 02/Sep/22  Resolved: 02/Sep/22

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-66297 Get rid of `maxSize` for shards Closed
Documentation Changes: Not Needed

 Description   
Original Downstream Change Summary

maxSize field from addShard command has been deprecated and InvalidOptions error is thrown in case user runs addShard

{ ... , maxSize: <value> }

.
maxSize field entry won't be generated in config.shards, and in case is present because of an upgrade from previous version (we do not delete the entry when upgrade) the field is ignored.
Every cluster related stats printing the max size of the shard do not provide this information anymore.

Description of Linked Ticket

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)


 Comments   
Comment by Anna Henningsen [ 02/Sep/22 ]

No impact.

Generated at Wed Feb 07 22:41:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.