|
Issue Links:
|
Depends
|
|
is depended on by
|
SERVER-36417
|
Drop pooled connections to nodes no l...
|
Blocked
|
Related
|
|
related to
|
SERVER-48975
|
Increase isSelf logging verbosity
|
Closed
|
|
is related to
|
SERVER-43632
|
Possible memory leak in 4.0
|
Closed
|
|
is related to
|
SERVER-35649
|
Nodes removed due to isSelf failure s...
|
Closed
|
|
| Assigned Teams: |
Replication
|
| Operating System: |
ALL
|
| Steps To Reproduce: |
Steps to reproduce:
1. Start a replica set on 4.0.9
2. Connect to the primary, then run rs.add("NEW_HOST:2017"). (NEW_HOST is a server that the replica set members can't connect to).
3. There will be heartbeat failure to this node. This is expected.
4. Run rs.remove("NEW_HOST:2017") to remove it from the replica set.
5. After this node is removed from the replica set, the replica set members still send heartbeat to this node, which is unexpected.
|
| Sprint: |
Repl 2019-07-01, Repl 2019-07-15, Repl 2019-07-29, Repl 2019-08-12, Repl 2019-09-23, Repl 2019-10-07, Repl 2019-10-21, Repl 2019-11-04 |
| Participants: |
|
| Case: |
|
| Linked BF Score: |
3
|