[SERVER-31107] Remove redundant stopBalancer call in hash_shard_unique_compound.js Created: 15/Sep/17 Updated: 29/Jan/18 Resolved: 20/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2017-10-02 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
ShardingTest in v3.2 defaults to disabling the balancer. There's no need to call stopBalancer when it is already disabled. This is causing a failure in the continuous step down suite, because stopBalancer does a write and cannot be retried when interrupted by a config primary step down. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 20/Sep/17 ] |
|
Backported |