[SERVER-73052] ShardingCatalogClient::getShardsThatOwnData...AtClusterTime() methods need a richer data structure to describe the returned Placement Metadata Created: 19/Jan/23  Updated: 29/Oct/23  Resolved: 07/Feb/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0-rc0

Type: Task Priority: Major - P3
Reporter: Paolo Polato Assignee: Enrico Golfieri
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-02-06
Participants:

 Description   

As per today, the getShardsThatOwnData...AtClusterTime() API methods of the ShardingCatalogClient return a set of ShardingIDs indicating which shards were serving data for the targeted namespace/cluster at a specific point in time.

Nevertheless, it such point in time is prior to the creation of the initial data stored in config.placementHistory, it is impossible to retrieve an accurate set of shard IDs.

As a fallback, the API methods will have to access the current content of config.shards, to compose an approximated value for the set of Sharding IDs. The returned placement metadata will then have to include an indication on whether they represent and exact or approximate description.



 Comments   
Comment by Githook User [ 07/Feb/23 ]

Author:

{'name': 'Enrico Golfieri', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-73052 ShardingCatalogClient::getShardsThatOwnData...AtClusterTime() methods need a richer data structure to describe the returned Placement Metadata
Branch: master
https://github.com/mongodb/mongo/commit/f314903119bfe09ee0e54c7c00f7f814c370efb5

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