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

Make sure shard key bounds are valid when committing `moveRange`

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.3.0-rc0, 6.0.6
    • 6.1.1, 6.0.4, 6.2.0-rc6
    • Sharding
    • None
    • Sharding EMEA
    • Fully Compatible
    • ALL
    • v6.2
    • Sharding EMEA 2023-02-06

    Description

      Before committing a chunk split, there is a check ensuring that the split point is a valid shard key.

      Since the auto-splitter has been eliminated and split points are now selected in the moveRange path, we must adapt the migration commit to also check that the new bounds are valid shard keys.

      Attachments

        Activity

          People

            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: