-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding, Upgrade/Downgrade
-
None
-
Cluster Scalability
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Resharding is incompatible with setFCV: Resharding refuses to start during kUpgrading/kDowngrading and setFCV aborts ongoing reshardings after entering kUpgrading/kDowngrading.
However this mutual exclusion is only exercised by a handful of tests
, so bugs/regressions have gone undetected in the past.
Either new tests (e.g. concurrency, passthrough tests that can run on FCV upgrade/downgrade suites) suites or executing the following issues would help cover this gap:
- SERVER-104171 Remove tag excluding balancer from setFCV concurrency tests
- SERVER-111230 reshardCollection may fail to clean up metadata on its temporary collection when aborted
- SERVER-130943 add_remove_shards hook does not work properly with concurrent setFCV
Tests that currently exercise resharding + setFCV (2026-07-23)
- Deterministic noPassthrough tests:
- Concurrency tests:
- random_ddl_setFCV_operations_with_metadata_check.js (setFCV+moveCollection)
- random_ddl_crud_setFCV_operations.js (setFCV+reshardCollection+unshardCollection) - since 2026-07-22.
- depends on
-
SERVER-111230 reshardCollection may fail to clean up metadata on its temporary collection when aborted
-
- Backlog
-
-
-
- Backlog
-
-
SERVER-104171 Re-enable JavaScript tests which were left disabled due to SERVER-88539
-
- Backlog
-
- related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Backlog
-