Allow relative weights greater than 100%, capping the absolute value to 256 which is the largest supported absolute weight.
Signed-off-by: Simon Horman <ho...@verge.net.au> --- doc/configuration.txt | 25 +++++++++++++------------ src/dumpstats.c | 7 ++++++- 2 files changed, 19 insertions(+), 13 deletions(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index f1a388e..61e8e4f 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -11369,18 +11369,19 @@ set timeout cli <delay> set weight <backend>/<server> <weight>[%] Change a server's weight to the value passed in argument. If the value ends with the '%' sign, then the new weight will be relative to the initially - configured weight. Relative weights are only permitted between 0 and 100%, - and absolute weights are permitted between 0 and 256. Servers which are part - of a farm running a static load-balancing algorithm have stricter limitations - because the weight cannot change once set. Thus for these servers, the only - accepted values are 0 and 100% (or 0 and the initial weight). Changes take - effect immediately, though certain LB algorithms require a certain amount of - requests to consider changes. A typical usage of this command is to disable - a server during an update by setting its weight to zero, then to enable it - again after the update by setting it back to 100%. This command is restricted - and can only be issued on sockets configured for level "admin". Both the - backend and the server may be specified either by their name or by their - numeric ID, prefixed with a sharp ('#'). + configured weight. Absolute weights are permitted between 0 and 256. + Relative weights must be positive with the resulting absolute weight is + capped at 256. Servers which are part of a farm running a static + load-balancing algorithm have stricter limitations because the weight + cannot change once set. Thus for these servers, the only accepted values + are 0 and 100% (or 0 and the initial weight). Changes take effect + immediately, though certain LB algorithms require a certain amount of + requests to consider changes. A typical usage of this command is to + disable a server during an update by setting its weight to zero, then to + enable it again after the update by setting it back to 100%. This command + is restricted and can only be issued on sockets configured for level + "admin". Both the backend and the server may be specified either by their + name or by their numeric ID, prefixed with a sharp ('#'). show errors [<iid>] Dump last known request and response errors collected by frontends and diff --git a/src/dumpstats.c b/src/dumpstats.c index 863de8e..81d8564 100644 --- a/src/dumpstats.c +++ b/src/dumpstats.c @@ -917,12 +917,17 @@ static int stats_sock_parse_weight_change_request(struct stream_interface *si, w = atoi(weight_str); if (strchr(weight_str, '%') != NULL) { - if (w < 0 || w > 100) { + if (w < 0) { warning = "Relative weight must be positive.\n"; status = STAT_CLI_PRINT; goto err; } + /* Avoid integer overflow */ + if (w > 25600) + w = 25600; w = sv->iweight * w / 100; + if (w > 256) + w = 256; } else { if (w < 0 || w > 256) { -- 1.7.10.4