Since the namespace is empty, this ends up sending a listCollections with a garbage filter
{ listCollections: 1, filter: { name: "$cmd.aggregate" }}
and also causes failures in the config stepdown suite, because the listCollections is sent over the legacy networking layer (DBClient) which does not have built-in retries on network errors.
- is duplicated by
-
SERVER-34603 Aggregate commands which run locally on mongos unnecessarily run listCollections against the primary shard
-
- Closed
-
- is related to
-
-
- Closed
-