acquiring distributed lock for upgrade process for 2.2->2.4 has very long timeout.

if the distributed lock to initiate the upgrade process can not be acquired for some reason (e.g. a config server is down) it continues to retry for up to 15 mins before failing completely.
for upgrade process we might want to make this fail more quickly so that it is clearer to the user what is happening, otherwise it is a bit concerning to see an upgrade process spam the logs with lots of lock acquisition failure messages.