If lock acquisition fails for anything other than LockStateChangeFailed, the sharding distributed lock manager will schedule an unlock in order to cleanup any potentially bad leftover state.

In case of errors, where we know that the lock attempt definitely did not modify any documents, we should not schedule this unlock attempt in order to reduce the amount of logging and mitigate log overflow such as the one described in SERVER-22971.