-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Execution Team 2022-03-21, Execution Team 2022-04-04
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.
- is related to
-
SERVER-62006 Support majority read for _mdb_catalog
- Closed
-
SERVER-62008 Support majority read for $indexStats
- Closed
-
SERVER-64980 Collectionless $listCatalog should not return catalog entries from non-chunk-owning shards
- Backlog
- related to
-
SERVER-69750 For certain index options, $listCatalog output could have inconsistent data type as $listIndexes
- Closed
-
SERVER-87088 add PIT lookups to list_catalog_read_concern.js
- Closed