Our aggregation code unconditionally passes down the collection's read preference to the operations layer. This is fine for replica sets because we use the write selector for aggregations with output stages ($out/$merge) but not for sharded clusters because the lower level will pass the read preference to the mongos.

I have verified that the a $out with read preference secondary does not work as expected against a sharded cluster and the output collection is not created.