-
Type: New Feature
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Upgrade/Downgrade
-
None
-
Fully Compatible
-
Storage NYC 2018-03-12
Currently, only incoming connections from last-stable binary version clients are closed upon bumping the featureCompatibilityVersion. Outgoing connections to last-stable binary version servers should be closed as well.
- depends on
-
SERVER-32601 Add the ability to tag and close outgoing connections within a sharded cluster
- Closed
- has to be done before
-
SERVER-32911 Remove heartbeat version field, "hbv", from the heartbeat command once outgoing connections to last-stable binaries are closed on FCV upgrade
- Backlog
- is duplicated by
-
SERVER-32910 Update multiVersion/feature_compatibility_version_lagging_secondary.js to use v3.6 and v4.0 binaries, rather than v3.4 and v4.0
- Closed
- is related to
-
SERVER-32729 Bump the replica set heartbeat version so a latest-FCV primary does not attempt to talk to a last-stable binary secondary
- Closed