-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14
-
35
-
2
While investigating uses of NaN in the balancer, it came up that if the user updates the maxChunkSize to a value not accepted by the balancer (NaN, -10, etc.), the balancer and all other operations that rely on the balancer configuration setting will fail until the setting is changed. These operations are:
- all balancer operations
- add shard
- chunk autosplitting and initial chunk splitting
- manual migrations
This ticket is to investigate whether this is a problem and if there is a way to reject the write of an invalid value rather than checking it at runtime.
- is related to
-
-
- Closed
-
- related to
-
SERVER-39122 Enforce schema on system collections
-
- Closed
-
-
-
- Open
-
-
SERVER-69163 Enforce Schema on System Collections
-
- Closed
-