All Job Schedulers of a cluster do not stop if they all have lost the database connection

Now, if a JobScheduler cluster member lose the database connection then it terminates after ~2 minutes.
Futher a new process is started and it waits for the database except the parameter "scheduler.cluster.restart_after_emergency_abort" is "false".

The wish is that the JobScheduler cluster member detects if all other cluster members have lost the connection too. In this case the JobScheduler should not stop. It should try to reconnect without restart.