[SERVER-66297] Get rid of `maxSize` for shards Created: 06/May/22  Updated: 14/Dec/23  Resolved: 07/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Enrico Golfieri
Resolution: Fixed Votes: 0
Labels: shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by COMPASS-6095 Investigate changes in SERVER-66297: ... Closed
Documented
is documented by DOCS-15601 [Server] Investigate changes in SERVE... Closed
Problem/Incident
causes SERVER-84187 Regression in balancer round storage ... Open
Related
related to SERVER-3566 Support draining if maxSize added or ... Closed
is related to SERVER-68430 remove maxSizeMb entry from sharding ... Closed
is related to SERVER-2246 Pay (more) attention to sharding maxSize Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-08-08, Sharding EMEA 2022-08-22, Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19
Participants:
Linked BF Score: 44
Story Points: 1.5

 Description   

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 Githook User [ 07/Sep/22 ]

Author:

{'name': 'Enrico Golfieri', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-66297 get rid of maxSize
Branch: master
https://github.com/mongodb/mongo/commit/8e70f09df8dc3ce2cfcb1ceb8a5c880d2e5a0037

Comment by Githook User [ 07/Sep/22 ]

Author:

{'name': 'Enrico Golfieri', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-66297 get rid of maxSize
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/5bfead7d6eecd3c5980134cd30e462c4bae6447c

Comment by Githook User [ 02/Sep/22 ]

Author:

{'name': 'Sviatlana Zuiko', 'email': 'sviatlana.zuiko@mongodb.com', 'username': 'szuiko'}

Message: Revert "SERVER-66297 get rid of maxSize"

This reverts commit 22f21e6e5a8086b3766485cc323ce9673587f30c.
Branch: master
https://github.com/mongodb/mongo/commit/56fa5811e2173dddfcb25689e15dafc680e9b0a6

Comment by Githook User [ 02/Sep/22 ]

Author:

{'name': 'Sviatlana Zuiko', 'email': 'sviatlana.zuiko@mongodb.com', 'username': 'szuiko'}

Message: Revert "SERVER-66297 get rid of maxSize"

This reverts commit ffc968d1256179241101fe132a370c01619877dd.
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/693e4ccb55c637698c5a4fff634be7daa4ae87e9

Comment by Githook User [ 01/Sep/22 ]

Author:

{'name': 'Enrico Golfieri', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-66297 get rid of maxSize
Branch: master
https://github.com/mongodb/mongo/commit/22f21e6e5a8086b3766485cc323ce9673587f30c

Comment by Githook User [ 01/Sep/22 ]

Author:

{'name': 'Enrico Golfieri', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-66297 get rid of maxSize
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/ffc968d1256179241101fe132a370c01619877dd

Comment by Garaudy Etienne [ 04/Aug/22 ]

ping me when this is done so I can file docs ticket(s)

Generated at Thu Feb 08 06:05:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.