[SERVER-47046] Add tests that mongos receives topology change info "immediately" Created: 23/Mar/20 Updated: 29/Oct/23 Resolved: 17/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc4, 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.4
|
||||
| Sprint: | Sharding 2020-04-06, Service arch 2020-04-20, Service arch 2020-05-04 | ||||
| Participants: | |||||
| Description |
|
Add the following test cases to check that mongos receives an isMaster reply "immediately" (or "quickly") after a RS topology change. In order to test this, we'll set the maxAwaitTimeMS to much higher than the default (5 mins). This will allow us to assert that mongos receives the isMaster replies because of a topology change rather than maxAwaitTimeMS. 1. Wait for mongos to discover RS primary, then call replSetStepUp on a secondary. |
| Comments |
| Comment by Githook User [ 29/Apr/20 ] |
|
Author: {'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}Message: (cherry picked from commit 02a81517543abd970408eab96ef3dd85e9b6a138) |
| Comment by Githook User [ 17/Apr/20 ] |
|
Author: {'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}Message: |