[SERVER-59822] [v4.4] shard_aware_init_secondaries.js does not wait for replica set to stabilize Created: 07/Sep/21 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Cluster Scalability
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
This test restarts the secondary. As a result, the primary doesn't see the secondary for a few seconds. Therefore, when the test ends and we call stopSet, the primary is prone to stepping down. If it does step down, it can cause problems when we are trying to freeze and validate the replica set. |