[SERVER-37413] awaitReplication in ReplSetTest::stopSet should wait on all nodes unless told otherwise Created: 01/Oct/18 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
It checks which nodes are alive and then waits on those here. If a node has a network blip or steps down or rolls back, then a node will not be considered alive that should. |
| Comments |
| Comment by Judah Schvimer [ 01/Oct/18 ] |
|
max.hirschhorn, the data consistency checks already detect which nodes are alive. This is saying they should not do this detection and rather be explicitly told which nodes to wait on, or else assume it should wait for all of them. |
| Comment by Max Hirschhorn [ 01/Oct/18 ] |
judah.schvimer, how are you proposing that the data consistency checks in ReplSetTest detect whether a node is alive and/or may still go into rollback? |