-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Sharding EMEA 2022-04-04, Sharding EMEA 2022-04-18
With the introduction of ranges in v6.0, chunks will have different sizes by design. This implies that when downgrading to pre-v6.0 versions, it will be needed to split again chunks according to the configured chunk size.
The idea is to run autoSplitVector on all the existing ranges in order to split them (if needed).
- depends on
-
SERVER-64437 Improve the logic to consume streaming actions on the Balancer secondary thread
- Closed
- related to
-
SERVER-64779 Review downgrade policy while defragmenting collection
- Closed