Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-44283

Change removeKeyRangeFromZone to use the bounds found from the fully extended shard key.

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 2019-12-16

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              haley.connelly Haley Connelly
              Reporter:
              blake.oler Blake Oler
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: