[DOCS-15601] [Server] Investigate changes in SERVER-66297: Get rid of `maxSize` for shards Created: 01/Sep/22 Updated: 13/Nov/23 Resolved: 28/Oct/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | David Hou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 1 year, 14 weeks, 5 days ago | ||||||||
| Epic Link: | DOCSP-22091 | ||||||||
| 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> }. Description of Linked TicketGet 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:
|
| Comments |
| Comment by Githook User [ 28/Oct/22 ] |
|
Author: {'name': 'davidhou17', 'email': '55004296+davidhou17@users.noreply.github.com', 'username': 'davidhou17'}Message: (
|
| Comment by David Hou [ 26/Oct/22 ] |
|
PR: https://github.com/10gen/docs-mongodb-internal/pull/2072 |
| Comment by Education Bot [ 07/Sep/22 ] |
|
Fix Version updated for upstream |
| Comment by Education Bot [ 02/Sep/22 ] |
|
Fix Version updated for upstream |
| Comment by Education Bot [ 01/Sep/22 ] |
|
Fix Version updated for upstream |