[SERVER-40732] recovery_preserves_active_txns.js should use awaitSecondaryNodes Created: 19/Apr/19 Updated: 29/Oct/23 Resolved: 22/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2019-04-22 | ||||
| Participants: | |||||
| Linked BF Score: | 16 | ||||
| Description |
|
The replsettest function "waitForState" waits for a node's state as reported by the primary. If we want to know if a secondary node is actually up, awaitSecondaryNodes should be used. In BF-12800, a secondary is restarted and "waitForState" reports it as up because the primary had not yet noticed it had gone down. |
| Comments |
| Comment by Githook User [ 22/Apr/19 ] |
|
Author: {'name': 'Matthew Russotto', 'username': 'mtrussotto', 'email': 'matthew.russotto@10gen.com'}Message: |