[SERVER-48242] Make stepping up secondary in range_deleter_interacts_correctly_with_refine_shard_key.js more robust Created: 15/May/20 Updated: 29/Oct/23 Resolved: 15/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc7, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | 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 | ||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||
| Sprint: | Sharding 2020-05-18 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 23 | ||||||||||||||||
| Description |
|
range_deleter_interacts_correctly_with_refine_shard_key.js makes a particular secondary node primary by running replSetStepUp on it, but this can fail if the node happens to be replicating more slowly than a majority of the set. Instead, the test should use ReplSetTest.stepUp() which accounts for this by both waiting for replication before issuing the step up command and retrying on failures. |
| Comments |
| Comment by Githook User [ 15/May/20 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit f35cd4090e5d379220f0471a126168988406c0b6) |
| Comment by Githook User [ 15/May/20 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |