Currently, the dist lock catalog retries the 'findAndModify' operations on NotMaster errors. In addition, in the dist lock manager there is a retry logic for the same set of errors.

The calls inside the dist lock catalog must be made to not retry because if the previous write succeeded, it would return a status indicating that the lock is busy, when in fact it is actually not. This throws off the outer retry logic.