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

random_moveChunk workloads should tolerate failed migrations because chunk's range is in use on recipient

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • Sharding 2019-04-08
    • 15

    Description

      At the beginning of a chunk migration, before clearing all documents from the range to be received, the recipient shard checks no documents in that range could be in use, throwing RangeOverlapConflict and failing the migration if so. The fsm workloads random_moveChunk_broadcast_delete/update_transaction.js randomly move chunks between shards while running multi writes without the shard key (which are versioned in a transaction), so migrations can fail with this code and the tests should tolerate that.

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: