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

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2019-08-12
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            James Heppenstall (Inactive)
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: