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

Best effort trigger shard refreshes after refining a collection's shard key

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.1
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2019-08-12

    Description

      So shards quickly pick up a new shard key, after refineCollectionShardKey updates the metadata for a collection, it should trigger refreshes on each shard that contains chunks for the refined collection. This isn't necessary for correctness, so triggering the refreshes can be best-effort and refineCollectionShardKey should return without waiting for each refresh to complete.

      SERVER-42369 tracks the work to guarantee these refreshes are eventually triggered.

      Attachments

        Activity

          People

            jamie.heppenstall@mongodb.com James Heppenstall (Inactive)
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: