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

Compare only epochs instead of full chunk versions in CollectionMetadata::checkChunkIsValid()

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.4.1, 3.5.1
    • 3.4.2, 3.5.2
    • Sharding
    • None
    • Fully Compatible
    • v3.4
    • Sharding 2017-01-02
    • 0

    Description

      The check on the shard that the chunk's version sent by the config is the same as what the shard sees is a little counter productive: we bump the version of a random chunk on the donor with every migration, so a chunk that hasn't even moved away and back might get rejected for a moveChunk or splitChunk.

      Instead, we should just compare the chunk's epochs to protect against moving a chunk on a collection that was dropped and recreated.

      Attachments

        Issue Links

          is depended on by

          Task - A task that needs to be done. SERVER-25673 Remove ChunkManager use in the MigrationManager

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-25527 Send the version of the chunk being moved as part of the shard moveChunk and splitChunk commands

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-27613 Remove unused 'chunkVersion' field sent in splitChunk command

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              esha.maharishi@mongodb.com Esha Maharishi (Inactive)
              esha.maharishi@mongodb.com Esha Maharishi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: