Currently the create collection coordinator retrieves collection information through the catalog cache that in turn relies on the sharding catalog client to retrieve this data. Since the catalog cache uses a combination of nearest read preference and snapshot read concern it could read stale data from a secondary node of the CSRS. If this happen the create collection coordinator would wrongly assume that the collection has not been committed yet.