[SERVER-25209] All CollectionMetadata functions that erase/add a chunk must be called through the MetadataManager Created: 22/Jul/16  Updated: 06/Dec/22  Resolved: 29/Jul/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: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done before SERVER-25010 Add a Notification object with each o... Closed
Assigned Teams:
Sharding
Participants:

 Description   

The MetadataManager must see every chunk range change (add/remove) to the active CollectionMetadata it maintains because the MetadataManager will be responsible for initiating range deletion and must maintain an accurate rangesToClean data structure.

For example, currently the MigrationSourceManager calls CollectionMetadata::cloneMigrate with the ScopedCollectionMetadata it gets from the MetadataManager. The MetadataManager does not currently update its rangesToClean when this happens.

Note: We may need to implement this, but temporarily comment out the line that actually adds/removes the range from rangesToClean. Until the the new CollectionRangeDeleter is committed and replaces the current RangeDeleter, the rangesToClean data structure would just grow larger and larger and never be reduced by a CollectionRangeDeleter.


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