On Thu, Jun 22, 2023, at 13:58, Frey, Rick E wrote: > The server needs to see its partner down before it will consider requests as > un-acked and begin responding such requests. If your standby server does not > see the other server as partner-down, the requests are not tracked as > un-acked even though they are not being processed by the primary server. If > you are testing failover, you’ll need to disrupt communication between > servers so standby host sees primary as partner-down. See previous thread > <https://lists.isc.org/mailman/htdig/kea-users/2023-January/003794.html> on > this topic.
This does not match the documentation. In the ARM it says that if max-unacked-clients is non-zero, then the server must notice at least that many unacked clients before it will transition its peer to the partner-down state. Disrupting communications is not sufficient to force that transition unless max-unacked-clients is set to zero. For the OP's configuration, using hot-standby, I'd probably just set max-unacked-clients to zero. This should be safe as long as the Kea servers are communicating with each other over the same path as the clients are communicating with them. The ARM explicitly suggests this too.
-- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
