[SERVER-2473] Avoid "no space left" on a shard Created: 03/Feb/11  Updated: 06/Dec/22  Resolved: 25/Jan/18

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

Type: Improvement Priority: Minor - P4
Reporter: Adrien Mogenet Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Any


Issue Links:
Duplicate
duplicates SERVER-2246 Pay (more) attention to sharding maxSize Closed
Related
is related to SERVER-3759 filesystem ops may cause termination ... Closed
Assigned Teams:
Sharding
Participants:

 Description   

Currently, we can give an option to limit global storage size on a shard.
Could it be possible to avoid full disk space errors in any case ?

If shard #1 and shard #2 get 100 Go of free space, but shard #3 only 50Go, the 3rd shard will be full before the #2 and #1 (that is logical).

But is there any reason to not avoid balancer to load data into shard #3 once it is completely full ?



 Comments   
Comment by Gregory McKeon (Inactive) [ 25/Jan/18 ]

Gone away since adding the "maxSize" parameter to addShared

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