[SERVER-51315] When removing nodes in tests, must take in to account automatic connection close Created: 02/Oct/20 Updated: 29/Oct/23 Resolved: 08/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0 |
| 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 2020-10-05, Repl 2020-10-19 | ||||
| Participants: | |||||
| Linked BF Score: | 47 | ||||
| Description |
|
Tests which expect to manipulate "REMOVED" nodes must take into account that removing a node will result in a disconnection if the connection is not marked hangUpOnStepDown: false. This disconnection occurs a few milliseconds after the node is marked "REMOVED", so it's hard to simply take into account. Best is probably to mark the test client connection with hangUpOnStepDown. This ticket covers fixing this problem for force_reconfig_skips_oplog_commitment.js initial_sync_succeeds_when_syncing_node_removed.js initial_sync_fails_when_syncing_node_removed.js |
| Comments |
| Comment by Githook User [ 08/Oct/20 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |