[SERVER-35390] Keep or update these Sharding-related FCV behaviors (tracking ticket) Created: 04/Jun/18  Updated: 29/Oct/23  Resolved: 02/Jul/18

Status: Closed
Project: Core Server
Component/s: Sharding
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: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-35116 Enumerate and remove Sharding-related... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-07-02, Sharding 2018-07-16
Participants:

 Description   
  • References to the latest FCV exist in sharding_catalog_manager_shard_operations.cpp in _validateHostAsShard. here. Update these to refer to the latest 4.2/4.0 FCV values.
  • References to the latest FCV exist in sharding_catalog_manager_shard_operations.cpp in addShard. Update these to refer to the latest 4.2/4.0 FCV values.
  • Update the setFeatureCompatibility command in shard_identity_rollback to refer to 4.2.
  • Update the last-stable FCV version in shardingtest.js to 4.0.


 Comments   
Comment by Blake Oler [ 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 [ 02/Jul/18 ]

Fixed with SERVER-35655 et al

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