-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
🟥 DDL, 🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
This is a follow-up to SERVER-131380 to determine the best way to handle resharding running during an FCV transition. SERVER-131380 implemented a short term fix, but in this ticket we should come up with more longer term solutions (SERVER-131380 description lists some long term solutions discussed).Â
important: The long term approach should be agreed upon with the CS team as it deals with resharding.Â
- depends on
-
SERVER-131380 Prevent resharding from starting during an FCV transition
-
- Closed
-
- is related to
-
SERVER-132143 Improve jstest coverage of resharding/setFCV mutual exclusion
-
- Needs Scheduling
-
- related to
-
SERVER-132223 Add tassert to ensure FCV when resharding commits is same as FCV at start (or is upgrading/downgrading from start FCV)
-
- Needs Scheduling
-