-
Type: New Feature
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Replication
-
Service Arch 2021-07-12, Service Arch 2021-08-09, Replication 2021-11-15, Replication 2021-11-29, Replication 2021-12-13, Replication 2022-01-10, Replication 2022-01-24, Replication 2022-02-07
-
(copied to CRM)
-
3
-
2
After a repl set reconfig, drop pooled connections to the removed node.
This would allow removal of a node, changes to host name resolution, and adding the node back with a new ip. Without changes, this either requires a long period to allow connection pools to age out, or manual intervention (if/when we implement SERVER-36416)
Acceptance Criteria:
Investigate the real level of effort for this ticket in the 'Investigating' status and if we provide replication with tools that they need to implement this behavior and add a comment with the amount of work required for this ticket.
- depends on
-
SERVER-41031 After an unreachable node is added and removed from the replica set, the other replica set members continue to send heartbeat to this removed node
- Open
-
SERVER-36415 Add dropConnections(const HostAndPort&) to the EgressTagCloser
- Closed
-
SERVER-59142 Add dropConnections API to TaskExecutor
- Closed
- is related to
-
SERVER-70297 Do not respond to heartbeat from removed node if it has the same version-term pair
- Closed