[SERVER-5004] balancer should check for stopped between chunk moves in current round Created: 17/Feb/12  Updated: 25/Jan/17  Resolved: 25/Feb/15

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

Type: Bug Priority: Minor - P4
Reporter: Greg Studer Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 3
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-7024 One balance round can move multiple c... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Participants:

 Description   

If there are many collections, turning off the balancer may result in many moves from the current balancer round - we should probably check the config server between chunk moves during a single round for stopped : true, to make the balancer more responsive.



 Comments   
Comment by Githook User [ 03/Mar/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-5004 Do not start new chunk moves if balancer is disabled mid balancing round

(cherry picked from commit bfe2e9e40bd3cf78a80db7c9676d12d7a70b7022)
Branch: v3.0
https://github.com/mongodb/mongo/commit/95f9c37168148ea948072b886a849f9fed071ea6

Comment by Githook User [ 25/Feb/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-5004 Do not start new chunk moves if balancer is disabled mid balancing round
Branch: master
https://github.com/mongodb/mongo/commit/bfe2e9e40bd3cf78a80db7c9676d12d7a70b7022

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