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

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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).

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: