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

Make move/merge/split chunk operations do partial chunk metadata reloads

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding
    • Fully Compatible

      move/merge/split operations use ShardingState::refreshMetadataNow, reloading the entire chunk metadata ~2 times per operation. I suspect this is very costly for collections with large numbers of chunks.

      ShardingState::refreshMetadataNow and ShardingState::onStaleShardVersion are the only two exposed means of refreshing the chunk metadata. Only the latter attempts to do incremental load.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: