-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding EMEA
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.
- related to
-
SERVER-57380 Improve "InvalidOptions: read concern level snapshot is only valid in a transaction" message during cluster incompatibility
- Closed