Commit 7b709fa9 authored by Thomas Markwalder's avatar Thomas Markwalder
Browse files

[v4_1_esv] Server now supports a failover split value of 256.

    Merges in rt36664
parent 9f1dbb07
......@@ -76,6 +76,9 @@ by Eric Young (eay@cryptsoft.com).
[ISC-Bugs #36712] Corrects Coverity reported "high" impact issues
[ISC-Bugs #36933] Corrects Coverity reported "medium" impact issues
- Server now supports a failover split value of 256.
[ISC-Bugs] #36664]
Changes since 4.1-ESV-R10rc1
- None
......
......@@ -1085,8 +1085,9 @@ void parse_failover_peer (cfile, group, type)
return;
}
split = atoi (val);
if (split > 255) {
parse_warn (cfile, "split must be < 256");
if (split > 256) {
parse_warn (cfile, "split must be between "
"0 and 256, inclusive");
} else {
memset (hba, 0, sizeof hba);
for (i = 0; i < split; i++) {
......
......@@ -669,7 +669,7 @@ The
statement
.RS 0.25i
.PP
.B split \fIindex\fR\fB;\fR
.B split \fIbits\fR\fB;\fR
.PP
The split statement specifies the split between the primary and
secondary for the purposes of load balancing. Whenever a client
......@@ -681,7 +681,9 @@ the secondary is responsible. The \fBsplit\fR value determines
how many of the leading bits are set to one. So, in practice, higher
split values will cause the primary to serve more clients than the
secondary. Lower split values, the converse. Legal values are between
0 and 255, of which the most reasonable is 128.
0 and 256 inclusive, of which the most reasonable is 128. Note that
a value of 0 makes the secondary responsible for all clients and a value
of 256 makes the primary responsible for all clients.
.RE
.PP
The
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment