Question dhcp failover sync time

Hi all,

question for dhcp failover.
if one node goes down and will be replaced with a new one.
I will test this scenario twice a day and in the first time, the dhcp failover doesn´t come up. It feels like a split brain.
My question is how often will there be synced between nodes. One node goes down the dhcp is working without interruption
I found this nice blog post how complicated is the isc failover

I have attached my config file.
Would it be better to say split 255 , to say one vyos is the dhcp master.

My version
VyOS 1.4-rolling-202311220309

### Autogenerated by dhcp_server.py ###

# For options please consult the following website:
# https://www.isc.org/wp-content/uploads/2017/08/dhcp43options.html
#
# log-facility local7;


ddns-update-style none;
option rfc3442-static-route code 121 = array of integer 8;
option windows-static-route code 249 = array of integer 8;
option wpad-url code 252 = text;
option rfc8925-ipv6-only-preferred code 108 = unsigned integer 32;

# Vendor specific options - Ubiquiti Networks
option space ubnt;
option ubnt.unifi-controller code 1 = ip-address;
class "ubnt" {
    match if substring (option vendor-class-identifier , 0, 4) = "ubnt";
    option vendor-class-identifier "ubnt";
    vendor-option-space ubnt;
}

# DHCP failover configuration
failover peer "internal-network" {
    primary;
    mclt 1800;
    split 128;
    address 192.168.2.3;
    port 647;
    peer address 192.168.2.2;
    peer port 647;
    max-response-delay 30;
    max-unacked-updates 10;
    load balance max seconds 3;
}

# Shared network configration(s)
shared-network LAN {
    authoritative;
    subnet 192.168.2.0 netmask 255.255.255.0 {
        option domain-name-servers 192.168.2.1;
        option domain-name "internal-network";
        option domain-search "en.example.com", ;
        option routers 192.168.2.1;
        default-lease-time 900;
        max-lease-time 900;
        pool {
            failover peer "internal-network";
            deny dynamic bootp clients;
            range 192.168.2.20 192.168.2.254;
        }
    }
    on commit {
        set shared-networkname = "LAN";
    }
}

ok I found this

add

omapi-port 7911;
in /run/dhcp-server/dhcpd.conf
restart service

start omshell

server localhost
port 7911
connect
new failover-state
set name = "internal-network"
open

you got this
and locate-state and partner-state is the important message.
but this is not very suitable to check this quick

obj: failover-state
name = "internal-network"
partner-address = 20:13:bb:23:a1:55:00:00
partner-port = 00:00:02:87
local-address = 70:12:bb:23:a1:55:00:00
local-port = 00:00:02:87
max-outstanding-updates = 00:00:00:0a
mclt = 00:00:07:08
load-balance-max-secs = 00:00:00:03
load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
partner-state = 00:00:00:02
local-state = 00:00:00:02
partner-stos = "e_Gg"
local-stos = 65:5f:35:ac
hierarchy = 00:00:00:00
last-packet-sent = 00:00:00:00
last-timestamp-received = 00:00:00:00
skew = 00:00:00:00
max-response-delay = 00:00:00:1e
cur-unacked-updates = 00:00:00:00