Description
Currently, if the master broker loose the database connection (for instance, in case of network outage), it doesn't stop.
Some users would prefer to stop the broker to avoid "dual" master (even for a short period of time).
I propose to introduce stopOnError on the database lock to stop the broker as soon as the lease database can't be updated.