This should be fairly rare, since lock documents generally exist after the first lock attempt, but is something that could prevent balancing progress in a cluster, for example. The lock document on the first config server is forced, and state set to 0, but on subsequent lock attempts the lock tournament step fails because contacting the second or third config server results in an empty document which we don't handle correctly.

Needs a simple reproduction case. Seems possible from a code audit.