There are certain cases where the state after a commit chunk operation is not known and the shard needs to do a majority write in order to obtain the latest config server optime. This particular write is not allowed to fail, because the shard's cached metadata and config server op time cannot be trusted.

In the case where a shutdown happens at the exact time of chunk commit the shard will not continue serving requests and therefore we should special case this and not fassert.