[DOCS-13356] Investigate changes in SERVER-43918: Upgrade/downgrade process for compound hashed shard keys Created: 21/Jan/20  Updated: 13/Nov/23  Resolved: 23/Apr/20

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 4.3.3, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Ravind Kumar (Inactive)
Resolution: Done Votes: 0
Labels: docs-installation, docs-sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-43918 Upgrade/downgrade process for compoun... Closed
Participants:
Days since reply: 3 years, 41 weeks, 6 days ago
Epic Link: DOCS: 4.4 Server Release Work
Story Points: 0.5

 Description   

Description

Downstream Change Summary

The users need to drop all the collections with compound hashed shard key before initiating a downgrade process. The setFCV command to 4.2 from 4.4 will fail with a warning if such a collection exists.

Description of Linked Ticket

As distinct from SERVER-43913, this should test the behaviour of compound hashed shard keys in a mixed-version cluster.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 23/Apr/20 ]

Author:

{'name': 'Ravind Kumar', 'email': 'ravind.kumar@mongodb.com', 'username': 'rkumar-mongo'}

Message: DOCS-13356: Downgrade Instructions for Compound Hashed Indexes + Sharding
Branch: master
https://github.com/mongodb/docs/commit/6ba98277abc9b438c56d780a93f6f827055bacf0

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