[SERVER-45746] Test waits for state to change into SECONDARY after stepdown but it should wait for PRIMARY Created: 24/Jan/20 Updated: 28/Jan/20 Resolved: 28/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2020-01-27, Sharding 2020-02-10 | ||||
| Participants: | |||||
| Linked BF Score: | 50 | ||||
| Description |
|
Before doing a transaction this test steps down the primary node and waits until it becomes secondary, however, the router might not find out about that election so the following transaction fails with a noMaster error. The test should wait until the mongos finds a primary, something like this test |
| Comments |
| Comment by Marcos José Grillo Ramirez [ 28/Jan/20 ] |
|
The test will not be changed because the BF was fixed by https://jira.mongodb.org/browse/SERVER-45080 |