[SERVER-35003] Consider making the balancer threshold to always be 1 Created: 15/May/18  Updated: 29/Oct/23  Resolved: 13/Aug/18

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

Type: Improvement Priority: Major - P3
Reporter: Randolph Tan Assignee: Sarah Zhou
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-08-27
Participants:

 Description   

This is the threshold in question

Additionally, when the balancer threshold is set to 1, there is no longer a need for the aggressiveBalancerHint.

Background:
Because of the way how thresholds are computed, it is possible that the balancer won't take action after a single new shard is added to the cluster. Lowering the threshold can help in this scenario. We should also remove the part where we take the ceiling of the threshold and keep the fractional component when comparing thresholds in order to not be overly aggressive.



 Comments   
Comment by Githook User [ 13/Aug/18 ]

Author:

{'name': 'Sarah Zhou', 'email': 'sarah.zhou@10gen.com'}

Message: SERVER-35003 Consider making the balancer threshold to always be 1
Branch: master
https://github.com/mongodb/mongo/commit/29d08f189860ae4e99aa5bc070b182c3249ce68a

Generated at Thu Feb 08 04:38:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.