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

moveChunk needs to send config optime when sending _recvChunkStart to destination shard

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.2.0-rc0
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding A (10/09/15)
    • 0

    Description

      If the migration is the first sharding-aware operation that the recipient shard is participating in, then the _recvChunkStart command it receives will make it sharding-aware and load the chunk data for the chunk being migrated for the first time. If the collection was only recently created and sharded, there's a risk that it could load out of date data for the collection, causing it to see no chunks for this collection, which causes the migration to fail with an obscure "data transfer error". If the source shard included the config server optime when it sent _recvChunkStart, then there'd be no risk of the recipient shard reading stale data.

      Attachments

        Activity

          People

            spencer@mongodb.com Spencer Brody (Inactive)
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: