[SERVER-29549] balancer ignoring maxSize setting? Created: 10/Jun/17 Updated: 27/Oct/23 Resolved: 27/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Crimson Glory | Assignee: | Randolph Tan |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Initial setup. 1. change maxSize of shard1 to A/2 After that the load balancer will start moving from shard2 to shard1 until 'A' size is reached, even if maxSize was changed to A/2. |
| Participants: |
| Description |
|
maxSize setting is ignored by the balancer. When does the balancer get notified of a maxSize change? |
| Comments |
| Comment by Crimson Glory [ 27/Jun/17 ] |
|
Thanks. You can close this ticket. |
| Comment by Randolph Tan [ 13/Jun/17 ] |
|
Hi, The balancer retrieves the maxSize setting at the beginning of a balancer round. If you modified the setting when a balancing round already started, it won't get reflected until the next balancing round. If you wish to synchronize a setting change and the balancer, you can stop the balancer first (wait for it to finish the current round - the sh.stopBalancer shell helper already does this for you). Also note that the maxSize setting does not prevent documents from being inserted to a shard, it only prevents balancer from moving chunks to this shard if the maxSize is reached. Let me know if you're still experiencing the issue after you followed the stopBalancer suggestion I just mentioned. Hope that helps! |