[SERVER-45994] Make stepdown/shutdown suites work better with ShardingTest teardown hooks Created: 05/Feb/20 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | cs-subteam1, sharding-common-backlog, sharding-nyc-subteam1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Cluster Scalability
|
| Operating System: | ALL |
| Participants: | |
| Story Points: | 2 |
| Description |
|
Currently, a couple of hooks get run in SharingTest.stop requires that config server and shard primaries are fully up (and repl monitor thinks they are) and the stepdown/shutdown suites makes running the hooks prone to running into errors. |