[SERVER-31068] make config server update fcv 'targetVersion' at beginning of _configsvrSetFeatureCompatibilityCommand Created: 12/Sep/17  Updated: 06/Oct/17  Resolved: 28/Sep/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.13
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-31208 FCV needs to durably store whether up... Closed
depends on SERVER-31209 need to store upgrade/downgrade in pr... Closed
is depended on by SERVER-30358 shardCollection should ask primary sh... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-10-02
Participants:

 Description   

The config server should update the fcv targetVersion field at the beginning of _configsvrSetFeatureCompatibilityCommand (in contrast, on shards, the targetVersion field will be updated during the setFeatureCompatibilityCommand).

In addition, the wire protocol version checks a mongod uses to determine what incoming wire versions to accept should be updated to accept only the highest wire version if the fcv targetVersion != the fcv version.

This prevents a 3.4 mongos from modifying the authoritative sharding metadata on the config server during upgrade or downgrade.



 Comments   
Comment by Esha Maharishi (Inactive) [ 28/Sep/17 ]

Will be fixed as part of SERVER-30793.

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