[SERVER-45942] Make migration_coordinator_failover.js wait for mongos to see new shard primary before running CRUD comamnds through mongos Created: 04/Feb/20 Updated: 29/Oct/23 Resolved: 04/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2020-02-10 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
This makes the test robust to things like both shard replica set nodes running for election at the same time and losing the first election, and therefore it taking longer than the 20 seconds that mongos waits to find a primary for a CRUD command for a new primary to be elected. |
| Comments |
| Comment by Githook User [ 04/Feb/20 ] |
|
Author: {'name': 'Esha Maharishi', 'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com'}Message: |