Merges in rt39669.
the MPL 2.0 license terms.
[ISC-Bugs #45541]
+- Load balancing for failover peers can now be disabled by setting
+ "load balance max secs" to 0. Doing so for both peers means both
+ servers will respond to all DHCPDISCOVERs or DHCPREQUESTs as soon as
+ they are received.
+ [ISC-Bugs #39669]
+
Changes since 4.3.0 (bug fixes)
- Tidy up several small tickets.
messages but not responding to some client requests, the other
failover peer will take over its client load automatically as the
clients retry.
+.PP
+It is possible to disable load balancing between peers by setting this
+value to 0 on both peers. Bear in mind that this means both peers will
+respond to all DHCPDISCOVERs or DHCPREQUESTs.
.RE
.PP
The
state->name);
fail_count++;
}
+
+ if (state->load_balance_max_secs == 0) {
+ log_info ("WARNING: load balancing will be disabled "
+ "for failover peer, %s, "
+ "because its load balance max secs is 0",
+ state->name);
+ }
}
if (fail_count) {
log_fatal ("Failover configuration sanity check failed");
}
+
}
void dhcp_failover_startup ()
}
#endif
- if (state->load_balance_max_secs < ec) {
+ if ((state->load_balance_max_secs == 0) ||
+ (state->load_balance_max_secs < ec)) {
return (1);
}