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

Ensure all shards eventually refresh metadata after shard key refine

    XMLWordPrintableJSON

Details

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

    Description

      To ensure shards eventually pick up the new shard key after a shard key refine, during _configsvrRefineCollectionShardKey an asynchronous task resilient to failover should be launched that is guaranteed to trigger a refresh for the refined collection if the shard key refine succeeds and becomes majority committed. This should use the PersistentTaskQueue from the resumable range deleter project.

      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:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: