The Sharding DDL coordinator for dropDatabase delegates to the local catalog layer the generation of the op entry about its completion, but this occurs before the sharding metadata changes are actually committed into the config server.

The order of events needs to be reversed to ensure that the opening of a change stream that targets a database being dropped will be resilient to the placement change under any timing condition.