-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
v8.0
-
CAR Team 2024-05-13, CAR Team 2024-05-27, CAR Team 2024-06-10, CAR Team 2024-06-24, CAR Team 2024-07-08, CAR Team 2024-07-22, CAR Team 2024-08-05, CAR Team 2024-08-19, CAR Team 2024-09-02, CAR Team 2024-09-16, CAR Team 2024-09-30
Test that movePrimary correctly behaves during upgrade/downgrade to/from v8.0 considering that there maybe some problematic interleaving due to unsharded collections being tracked or not.
- depends on
-
SERVER-95544 setFeatureCompatibilityVersion, createCollection and moveCollection could cause a 3-way deadlock in config shards
- In Code Review
-
SERVER-91997 moveCollection could cause a deadlock with concurrent setFeatureCompatibilityVersion command
- Closed
-
SERVER-92370 Move primary might leave garbage after fcv dowgrade
- Closed