[SERVER-57381] Make the wrong upgrade/downgrade order of a sharded cluster user-friendly Created: 03/Jun/21  Updated: 06/Dec/22  Resolved: 12/Nov/21

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

Type: Improvement Priority: Major - P3
Reporter: Dmitry Agranat Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Do Votes: 0
Labels: 5.0-dogfooding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-57380 Improve "InvalidOptions: read concern... Closed
Assigned Teams:
Sharding EMEA
Participants:

 Description   

Currently, we do not prevent the wrong upgrade/downgrade order of a sharded cluster. Given the devastating impact of making a mistake with the documented order, and the lack of actionable log messages to indicate what has happened, we might consider developing a mechanism to make the wrong upgrade/downgrade order of a sharded cluster user-friendly.



 Comments   
Comment by Connie Chen [ 12/Nov/21 ]

This is not possible as we cannot predict every incompatibility between binaries for every release.

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