[DOCS-10916] Check featureCompatibilityVersion on all replica set members before replacing binaries during upgrade Created: 18/Oct/17  Updated: 29/Oct/23  Resolved: 14/Dec/17

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 3.6

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: release-notes
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by DOCS-10840 Docs for SERVER-30894: Implement comm... Closed
Participants:
Days since reply: 6 years, 9 weeks ago
Story Points: 1

 Description   

In the 3.6 downgrade instructions for replica sets, users are directed to check that the featureCompatibilityVersion is 3.4 on each member of the replica set before replacing the binaries with version 3.4. Likewise, when upgrading to 3.6, users should be directed to check that the featureCompatibilityVersion is 3.4 on each member of the replica set before replacing the binaries with version 3.6. Similarly for replica set members in a sharded cluster.



 Comments   
Comment by Githook User [ 13/Dec/17 ]

Author:

{'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-10916: check fcv on each member for upgrade docs
Branch: master
https://github.com/mongodb/docs/commit/7b4d805e773f7386fd518e21a0994c68c621159c

Comment by Ravind Kumar (Inactive) [ 09/Nov/17 ]

We sort of cover this generally under the Prerequisites for each of the instructions, but looking at the linked section I don't see why we can't provide step-by-step details.

ToDo:

For each of the upgrade tutorials, expand the Prereq blurb on featureCompatibilityVersion to follow the example shown on the downgrade docs

Generated at Thu Feb 08 08:01:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.