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

Index operations should only abort migrations of first chunk to a shard

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding

    Description

      From the design for Each Shard has Correct Indexes:

      Serializing entire migrations and index operations is only necessary when the recipient is receiving its first chunk because the shard versioning protocol will guarantee all shards with chunks will be targeted by index operations. So as an optimization, only the migration of the first chunk to a shard needs to be serialized with index operations (beyond existing serialization around entering the migration critical section).

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: