[SERVER-11113] Shard maxSize should be more accurate wrt space used/free Created: 09/Oct/13  Updated: 06/Dec/22  Resolved: 15/Nov/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-35431 rollback does not correct sizeStorer ... Backlog
Assigned Teams:
Sharding
Participants:

 Description   

Currently this value is taken from the server mapped memory number and results in no chunks being moved to the shard even if there is room in existing files (from deleted extents or docs).

Taking the sum of each databases datasize would be a better I believe.


Generated at Thu Feb 08 03:24:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.