[SERVER-26769] Balancer should load balancer settings before recovering migrations on failover Created: 25/Oct/16  Updated: 08/Nov/16  Resolved: 26/Oct/16

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

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2016-10-31
Participants:
Linked BF Score: 0

 Description   

On failover, the new config primary recovers migrations and uses the BalancerConfiguration class' default maxChunkSize of 64 here without trying to load any maxChunkSize user setting from config.settings. Thus, a chunk larger than what the user has defined as jumbo may get moved.

If the new primary was primary previously, it may have the correct maxChunkSize value set in the BalancerConfiguration instance: though it would be stale, whether right or wrong.

BalancerConfiguration::refreshAndCheck should be called before balancer recovery, as it is done before running every auto balancing round.



 Comments   
Comment by Githook User [ 26/Oct/16 ]

Author:

{u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}

Message: SERVER-26769 Balancer loads balancer settings before recovery and accepting/starting new migrations
Branch: master
https://github.com/mongodb/mongo/commit/d187c9ee45046a32c2fde033550f4ddbc6229794

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