[SERVER-59877] Increase the election timeout period in atlas_snapshot_workflows.js Created: 10/Sep/21 Updated: 06/Dec/22 Resolved: 13/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v5.0
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 35 | ||||||||
| Description |
|
atlas_snapshot_workflows.js uses a small election timeout period to speed up the test. However, this can also increase the frequency of unexpected step-downs. We should increase the election timeout slightly. Also, the checkReplicaSets method is always called with a calculation of the live secondaries appearing right before it is called, such as here. This can be moved inside the method, after the getPrimary call to improve synchronization. This isn't necessary to fix the bug, but can be investigated. |