[SERVER-37472] Improve behavior if user downgrades to 4.0 binary without setting FCV to 4.0 Created: 04/Oct/18  Updated: 29/Oct/23  Resolved: 02/Nov/18

Status: Closed
Project: Core Server
Component/s: Upgrade/Downgrade
Affects Version/s: 4.0.3
Fix Version/s: 4.0.5, 4.1.5

Type: Improvement Priority: Minor - P4
Reporter: Eric Milkie Assignee: Natalie Tsvetkova
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0
Sprint: Sharding 2018-10-22, Sharding 2018-11-05, Sharding 2018-11-19
Participants:

 Description   

Currently, if a user tries to run a 4.0 mongod binary on data files from FCV 4.2, the following messages appear in the log:

2018-10-04T08:40:21.447-0400 F STORAGE  [initandlisten] BadValue: Invalid value for version, found 4.2, expected '4.0' or '3.6'. Contents of featureCompatibilityVersion document in admin.system.version: { _id: "featureCompatibilityVersion", version: "4.2" }. See http://dochub.mongodb.org/core/4.0-feature-compatibility.
2018-10-04T08:40:21.447-0400 F CONTROL  [initandlisten] ** IMPORTANT: UPGRADE PROBLEM: Unable to parse the featureCompatibilityVersion document. The data files need to be fully upgraded to version 3.6 before attempting an upgrade to 4.0. If you are upgrading to 4.0, see http://dochub.mongodb.org/core/4.0-upgrade-fcv.



 Comments   
Comment by Githook User [ 13/Nov/18 ]

Author:

{'name': 'natalie.tsvetkova', 'email': 'natalie.tsvetkova@mongodb.com', 'username': 'ntsvetko'}

Message: SERVER-37472: Improve behavior if user downgrades to 4.0 binary without setting FCV to 4.0

(cherry picked from commit bda182eaab096c34f57efe94f5e0a8022c54bcc3)
Branch: v4.0
https://github.com/mongodb/mongo/commit/d8fb9151e857590b80f4bb8dea82e6782e534ef8

Comment by Githook User [ 31/Oct/18 ]

Author:

{'name': 'natalie.tsvetkova', 'email': 'natalie.tsvetkova@mongodb.com', 'username': 'ntsvetko'}

Message: SERVER-37472: Improve behavior if user downgrades to 4.0 binary without setting FCV to 4.0
Branch: master
https://github.com/mongodb/mongo/commit/bda182eaab096c34f57efe94f5e0a8022c54bcc3

Comment by Eric Milkie [ 05/Oct/18 ]

Something like that, yes. At the very minimum, we shouldn't print the message about having upgraded from prior to 3.6.

Comment by Kaloian Manassiev [ 05/Oct/18 ]

milkie, the messaging improvement you have in mind here would be to make it say something like this, right:

You must have downgraded your binaries without downgrading your FCV to a version, which is supported to that binary. Please restart using the version supporting FCV in question and follow the downgrade instructions from the documentation

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