[SERVER-49430] Running hang analyzer in awaitSecondaryNodesForRollbackTest prevents further connections to nodes Created: 10/Jul/20 Updated: 29/Oct/23 Resolved: 14/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | Vesselina Ratcheva (Inactive) |
| 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 2020-08-10, Repl 2020-08-24 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
In the ReplSetTest.awaitSecondaryNodesForRollbackTest function, we first call awaitSecondaryNodes, and if that times out, we then enter this section of logic to check for an unrecoverable rollback scenario. If the first awaitSecondaryNodes call times out, though, we trigger the hang analyzer which will suspend the mongod processes that we attach to. This prevents us from connecting to the nodes to run commands to check for unrecoverability. We should disable the hang analyzer for this awaitSecondaryNodes call (we can consider using MongoRunner.runHangAnalyzer.disable()), so that we can still connect to and run commands against nodes even after it times out. |
| Comments |
| Comment by Githook User [ 14/Aug/20 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}Message: |
| Comment by William Schultz (Inactive) [ 10/Jul/20 ] |
|
This issue appeared a few times in my patch build here. |