|
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
|
|
Roger that. Will keep that in mind when working on this ticket.
|
|
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.
|
|
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
|
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.