[SERVER-64342] Minor fix related to migrations performed by the defragmentation cmd Created: 09/Mar/22  Updated: 26/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: RECOVERING-PM-1633, oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-78495 Throw out vestiges of enableFinerGrai... In Code Review
Assigned Teams:
Catalog and Routing
Sprint: Sharding EMEA 2022-03-21, Sharding EMEA 2022-04-04
Participants:

 Description   

When the defragmentation logic performs a moveChunk, it invalidates the routing information associated to the destination shard but it doesn't invalidate the one associated to the source shard.

This is not a problem right now because the invalidation that it's being done there is just advancing the time in store and it is not actually needed to do it twice. However, this is not optimal for SERVER-64108 because this ticket will invalidate parts of the latest cached chunk manager.


Generated at Thu Feb 08 06:00:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.