[SERVER-35655] Update FCV constants throughout server code. Created: 18/Jun/18  Updated: 29/Oct/23  Resolved: 02/Jul/18

Status: Closed
Project: Core Server
Component/s: Sharding, Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: 4.1.1

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: branch-4.0, post-branch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-35884 Re-enable part of the set_feature_com... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-07-02, Sharding 2018-07-16
Participants:

 Description   

This process includes:

  • Adding FCV 4.2.
  • Removing FCV 3.6.
  • Setting FCV 4.0 to be the default value of the FCV parameter for new shard servers.
  • Updating "latest" FCV to be 4.2 and "last-stable" FCV to be 4.0.
  • Changing generic references to refer to the latest upgraded and downgraded versions.


 Comments   
Comment by Githook User [ 02/Jul/18 ]

Author:

{'username': 'BlakeIsBlake', 'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com'}

Message: SERVER-35655 Update FCV constants throughout server code.
SERVER-35169 Bump wire protocol version for 4.2.
SERVER-35752 Ensure tests that rely on FCV pass after updating FCV constants.
SERVER-35163 Unblacklist tests that expect FCV version to differ between "last-stable" and "latest."
SERVER-34984 Update major_version_upgrade.js to call setFCV to the latest FCV.
SERVER-35656 Ensure a 4.0 mongos crashes upon attempting to connect to an FCV 4.2 cluster.
SERVER-35404 Re-enable the sharding_last_stable_mongos_and_mixed_shards suite.
Branch: master
https://github.com/mongodb/mongo/commit/53a34c4f01d6b18df4c4800df9a72b1eff07fb6a

Comment by Blake Oler [ 18/Jun/18 ]

Roger that. Will keep that in mind when working on this ticket.

Comment by Eric Milkie [ 18/Jun/18 ]

That previous ticket lived in a world where the FCV could have been queried "unsafely", so a default other than unset was necessary for some cases.

Comment by Blake Oler [ 18/Jun/18 ]

milkie that is correct. Refer to this previous ticket for the 4.0 Upgrade/Downgrade project which uses similar verbiage. https://jira.mongodb.org/browse/SERVER-32741

Comment by Eric Milkie [ 18/Jun/18 ]

Setting FCV 4.0 to be the default value of the FCV parameter.

Why wouldn't we make the default "kUnset"? Or are you referring to the value of the written FCV document for new shard servers – "4.0" is correct for that case.

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