[SERVER-26913] Make move/merge/split chunk operations do partial chunk metadata reloads Created: 04/Nov/16  Updated: 06/Dec/22  Resolved: 04/Nov/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-26791 move/split/mergeChunk commands do a f... Closed
Assigned Teams:
Sharding
Backwards Compatibility: Fully Compatible
Participants:

 Description   

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.


Generated at Thu Feb 08 04:13:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.