-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Labels:
-
Fully Compatible
-
Sharding 2019-12-16
When adding a range to a zone, we extend the shard key to include all fields then use that range in the update query.
When removing a range from a zone, we extend the shard key but don't use the extended shard key in the remove query.
We should use the full range in removing a range from a zone in order to make behavior consistent across these two operations.
With the completion of the ticket, we should also remove the RangeOverlapConflict retry logic on the test that will be committed in SERVER-44062.
- is duplicated by
-
SERVER-44454 updateZoneKeyRange is inconsistent with updating and deleting tags when tag ranges are prefix for shard key
- Closed