Major Description
Every now and then I observe cases where a MongoDB primary becomes unavailable, one of the secondary becomes the new primary rather quickly, but Oak is still unable to update its lease in the clusterNodes collection and then needs to be restarted. It appears, the lease update can be stuck and waiting for a response from the failing primary, e.g. due to a network issue.
