[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: |
|
||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently, we can give an option to limit global storage size on a shard. 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 |