[SERVER-32636] Close outgoing connections to servers running the last-stable binary version on setFeatureCompatibilityVersion to the latest featureCompatibilityVersion Created: 10/Jan/18  Updated: 30/Oct/23  Resolved: 28/Feb/18

Status: Closed
Project: Core Server
Component/s: Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: 3.7.3

Type: New Feature Priority: Major - P3
Reporter: Maria van Keulen Assignee: Maria van Keulen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-32601 Add the ability to tag and close outg... Closed
Duplicate
is duplicated by SERVER-32910 Update multiVersion/feature_compatibi... Closed
Gantt Dependency
has to be done before SERVER-32911 Remove heartbeat version field, "hbv"... Backlog
Related
is related to SERVER-32729 Bump the replica set heartbeat versio... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-03-12
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 28/Feb/18 ]

Author:

{'email': 'maria@mongodb.com', 'name': 'Maria van Keulen', 'username': 'mvankeulen94'}

Message: SERVER-32636 Close outgoing connections to earlier binVersion servers
Branch: master
https://github.com/mongodb/mongo/commit/d1ba78a5a83b58275aed657d71b58a57847e7027

Comment by Dianna Hohensee (Inactive) [ 09/Feb/18 ]

SERVER-32910 will be done as part of this ticket, because it is test coverage. SERVER-32910 can then be closed without work.

Comment by Maria van Keulen [ 07/Feb/18 ]

multiVersion/feature_compatibility_version_lagging_secondary.js will be blacklisted as part of SERVER-32597 to facilitate removal of the featureCompatibilityVersion 3.4 value. Once the test is updated to use the correct fCV values, it should be re-enabled as part of this ticket.

Comment by Dianna Hohensee (Inactive) [ 25/Jan/18 ]

Additionally, when this is complete, multiVersion/feature_compatibility_version_lagging_secondary.js should be updated to use latest (v4.0) and last-stable (v3.6) binaries, rather than latest and 3.4 binaries, which is currently the only reason it isn't failing in v4.0.

Comment by Dianna Hohensee (Inactive) [ 22/Jan/18 ]

If this is complete, the heartbeat version field to prevent latest FCV to last-stable FCV heartbeats can be removed – see comment in SERVER-31631.

Generated at Thu Feb 08 04:30:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.