Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Sharding
Labels:
None

Assigned Teams:

Sharding EMEA

The work for ~~SERVER-32198~~ will decouple the direct dependency of non-sharding code on CollectionMetadata and all the interactions of non-sharding consumers with sharding will be going only through CollectionShardingState and specifically through the getOwnershipFilter and getCollectionDescription interfaces.

This work in this ticket is one level below the CollectionShardingState implementation on shards and is to remove all dependencies from CollectionShardingState on CollectionMetadata and push that interaction to be done through calls to the FilteringMetadataService.

After this ticket is done, there should be no more CollectionMetadata calls and the MetadataManager can be thrown out.

depends on

SERVER-46204 Implement the facade of the FilteringMetadataService

Closed

SERVER-46206 Make the FilteringMetadataService participate in the migration commit

Closed

SERVER-46207 Make the CatalogCache efficiently provide filtering metadata for a shardVersion

Closed

SERVER-46208 Remove the ShardServerCatalogCacheLoader from the CatalogCache refresh code path

Closed

SERVER-46209 Ensure all sharding consumers are able to handle SnapshotTooOld/StaleShardVersion exceptions

Closed

Assignee:: [DO NOT USE] Backlog - Sharding EMEA

Reporter:: Kaloian Manassiev

Participants:: [DO NOT USE] Backlog - Sharding EMEA, Kaloian Manassiev

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: Feb 16 2020 07:41:53 AM UTC

Updated:: Dec 06 2022 02:35:40 AM UTC

Resolved:: Feb 17 2022 04:31:17 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates