[SERVER-50505] Make the CatalogCache return ChunkManager(s) directly Created: 25/Aug/20  Updated: 29/Oct/23  Resolved: 01/Sep/20

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

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-09-07
Participants:

 Description   

Currently, the CatalogCache returns an intermediate "combo" object called CachedCollectionRoutingInfo for its collection routing methods. We should go in a direction where the ChunkManager is the only thing used for routing, so we should make the CatalogCache return it directly instead.

As a follow-up step, we should remove all places which differentiate between sharded and unsharded collections and push that logic in the ChunkManager's routing methods. That way when we make all collections be sharding-aware, we will only have to make changes there.



 Comments   
Comment by Githook User [ 01/Sep/20 ]

Author:

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

Message: SERVER-50505 Make the CatalogCache return ChunkManager(s) directly

... instead of returning the intermediate CachedCollectionRoutingInfo
class. The ChunkManager should be the only class used for routing.
Branch: master
https://github.com/mongodb/mongo/commit/9cb82d2e8680717d3002459ba5fdb16036183a17

Generated at Thu Feb 08 05:22:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.