[SERVER-47660] Upgrade 3.4.2 to 3.6.17 problem Created: 20/Apr/20  Updated: 06/Dec/22  Resolved: 20/Apr/20

Status: Closed
Project: Core Server
Component/s: Upgrade/Downgrade
Affects Version/s: 3.4 Required
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: dor cohen Assignee: Backlog - Triage Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Triage
Participants:

 Description   

hi ,

we want to upgrade our sharded cluster from 3.4.2 to 3.6.17,

we tried following this https://docs.mongodb.com/manual/release-notes/3.6-upgrade-sharded-cluster/ with the ops manager

but when we tried to change the binaries from 3.4 to 3.6 in the first config server there was a problem and it didnt start up with this error 

UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.4 before attempting an upgrade to 3.6; see http://dochub.mongodb.org/core/3.6-upgrade-fcv for more details.

can you help us?



 Comments   
Comment by Carl Champain (Inactive) [ 20/Apr/20 ]

Hi dorc141414@gmail.com,

It seems that featureCompatibilityVersion is not set to 3.4. The error also provides this link.

To set or update featureCompatibilityVersion, run the following command on the mongos:

db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } )

That said, the SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the MongoDB Community Forums or on Stack Overflow with the mongodb tag.
 
Thank you,
Carl

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