[SERVER-64404] improve sharding support $listCatalog aggregation stage Created: 10/Mar/22  Updated: 29/Oct/23  Resolved: 29/Mar/22

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

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-69750 For certain index options, $listCatal... Closed
is related to SERVER-62006 Support majority read for _mdb_catalog Closed
is related to SERVER-62008 Support majority read for $indexStats Closed
is related to SERVER-64980 Collectionless $listCatalog should no... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-03-21, Execution Team 2022-04-04
Participants:

 Description   

We introduced the $listCatalog aggregation stage in SERVER-62006 to provide read majority access to the durable catalog to support an internal application for migrating sharded clusters.

There are still some gaps in this new aggregation stage that need to be addressed in the context of a sharded cluster, especially when there is active chunk migration in progress:

  • Ensuring the aggregation stage is defined to run on all shards.
  • Provide identifying shard information in the stage results.
  • Take into account sharding-specific information in collections such as config.databases and config.collections.

The initial work included tests that run in jsCore and most of the associated passthroughs. A new test in the jstests/sharding suite would help with coverage over the sharding-specific enhancements.



 Comments   
Comment by Githook User [ 29/Mar/22 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-64404 Add collection-level `$listCatalog`
Branch: master
https://github.com/mongodb/mongo/commit/5157deaa6adcce380f01f4736efbdf3c473e11bf

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