It may happen that a create collection coordinator successfully commits the metadata of a new sharded collection on the config server (here or here) and releases the critical section right before stepping down. On resume, the collection is identified as already sharded and the critical section re-released. However, if a migration kicks in and acquires the critical section right before issuing the release, the following invariant is triggered.