-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
removeKeyRangeFromZone called from updateZoneKeyRange command extends the range to the full shard key but skips checkHashedShardKeyRange.
- Shard {x: "hashed"} and add a zone range with valid NumberLong bounds.
- updateZoneKeyRange is run with raw bounds {min {x: 0}, max {x: 25}, zone: null} instead of using NumberLong hashed bounds.
- The command returns ok: 1 with tag still in config.tags.
The user impact is false success instead of failing with BadValue or InvalidOptions.
To fix this we can use extendAndValidateZoneRange for validations added in SERVER-138623