[SERVER-32447] Create mock up for the multi versioned routing table components Created: 21/Dec/17  Updated: 30/Oct/23  Resolved: 16/Jan/18

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

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-01-01, Sharding 2018-01-15, Sharding 2018-01-29
Participants:

 Description   

Match the API so we have a mock to work with and test against while its being built.
One of the ideas:

  • Make ChunkManager constructor to take ClusterTime and so the instance of the ChunkManager will contain routing only <= the provided time.
  • Add a method getTime() that will return the latest ClusterTime persisited i.e. used in a versioned data of the chunks that are used to create this manager. This time is <= then the provided to the c-tor time


 Comments   
Comment by Githook User [ 16/Jan/18 ]

Author:

{'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}

Message: SERVER-32447 Add a mock CatalogCache::getCollectionRoutingInfoAt method

The added method always returns the routing information at the latest
timestamp.
Branch: master
https://github.com/mongodb/mongo/commit/7f4e454907f14a5a82195d15e6ee96cbcd6d4d5b

Comment by Kaloian Manassiev [ 21/Dec/17 ]

Let's not change the constructor or the API of the ChunkManager yet. Instead, how about we add a variant of the getCollectionRoutingInfo call, which accepts a clusterTime? Maybe name it also getColectionRoutingInfoAtTime.

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