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

If a chunk has been split since a moveChunk was sent to a shard, you can get an error message with "This indicates corrupted metadata"

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2016-10-31
    • 0

    Description

      In the MigrationSourceManager there is a check here that assumes if the shard has a chunk with the minKey, but doesn't have a maxKey corresponding to the command's maxKey, that the metadata is corrupted.

      We should check whether there's another chunk with a minKey matching the maxKey, and if so, assume that the chunk was split and return a more benign error message.

      Attachments

        Activity

          People

            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: