-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Execution Team 2022-04-04
For example if the primary shard does not own any chunks for the collection being queried, $indexStats will not target that shard. Then if the actual collection is unsharded, the actualCollection field of the CollectionUUIDMismatch will not be populated even though it should be. More generally, this can occur if there are no shards that contain chunks for both collections. This should be able to be solved with the same approach as SERVER-63285.
- is depended on by
-
SERVER-64875 Support specifying collectionUUID in more aggregates on sharded clusters
- Closed
- related to
-
SERVER-62563 Support sharding for collectionUUID parameter of aggregate command
- Closed
-
SERVER-63285 Ensure CollectionUUIDMismatch error from write commands does not omit the actual collection even if unsharded
- Closed