[SERVER-44283] Change removeKeyRangeFromZone to use the bounds found from the fully extended shard key. Created: 28/Oct/19  Updated: 29/Oct/23  Resolved: 05/Dec/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.3.3

Type: Improvement Priority: Major - P3
Reporter: Blake Oler Assignee: Haley Connelly
Resolution: Fixed Votes: 0
Labels: neweng, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-44454 updateZoneKeyRange is inconsistent wi... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-12-16
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 05/Dec/19 ]

Author:

{'name': 'Haley Connelly', 'username': 'haleyConnelly', 'email': 'haley.connelly@10gen.com'}

Message: SERVER-44283 Change removeKeyRangeFromZone to use the bounds found from the fully extended shard key.
Branch: master
https://github.com/mongodb/mongo/commit/4e707f244d88b112b15080afa2361210715b12d2

Generated at Thu Feb 08 05:05:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.