[SERVER-24105] Remove balancer manipulations in multi_mongos2.js that do nothing Created: 09/May/16 Updated: 16/May/16 Resolved: 09/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.6 |
| 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: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 14 (05/13/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The balancer will not move chunks unless there is at least a difference of 2 between the number of chunks two shards possess. The balancer is doing nothing in multi_mongos2.js because it is only started after manual split/moveChunks are performed that rebalance the number of chunks on shards. The balancer being enabled is unnecessary and prevents multi_mongos2.js from being in the sharding_continuous_config_stepdown suite. |
| Comments |
| Comment by Githook User [ 09/May/16 ] |
|
Author: {u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}Message: |
| Comment by Dianna Hohensee (Inactive) [ 09/May/16 ] |
|
This looks like the original commit for the balancer code in the test: https://github.com/mongodb/mongo/commit/5d78616641af1259b47869c80c44c3cca4eacfe1#diff-451dd9fc6a2490042b3620de6f601e86 Looks like it was added to protect the test from the balancer that used to be automatically enabled. Stops and starts were wrapped around the split/moveChunk command pairs. Seems unnecessary now. |