[SERVER-31923] auto_rebalance_parallel_replica_sets.js must prevent shard primary stepdowns Created: 10/Nov/17 Updated: 27/Oct/23 Resolved: 02/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Janna Golden |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | Sharding 2020-04-20 | ||||
| Participants: | |||||
| Linked BF Score: | 20 | ||||
| Description |
|
auto_rebalance_parallel_replica_sets.js expects the balancer to perform two migrations in a single balancing round. However, if a recipient shard primary steps down, one of those migrations will fail – this occurred in BF-6744 |
| Comments |
| Comment by Janna Golden [ 02/Apr/20 ] |
|
As a part of |
| Comment by Ratika Gandhi [ 29/Jul/19 ] |
|
As part of wider tactic of using votes:0 to avoid handling spurious stepdowns, we should fix this too. |