load-increase-factor

1

Specifies the factor by which a single recovered server instance is incrementally included in load distribution. Allowed values are decimal numbers between 0 and 1. 

The load factor starts at zero and increases by load-increase-factor every load-factor-increase-period-in-seconds until it reaches 1. For example, if load-increase-factor is set to 0.1 and load-factor-increase-period-in-seconds is set to 60, it takes ten minutes for a recovered instance to be fully included in load distribution.

The load-increase-factor and load-factor-increase-period-in-seconds properties are applicable to all SIP requests and to HTTP requests for converged applications only if data-centric rules are specified.

The load-increase-factor and load-factor-increase-period-in-seconds properties have no effect on the round-robin algorithm, which is applicable to HTTP requests for pure web applications.

load-factor-increase-period-in-seconds

0

Specifies the number of seconds between load factor increases for a recovered server instance. 

If load-factor-increase-period-in-seconds is set to zero, load-increase-factor has no effect. The load factor for the recovered instance becomes 1 immediately.

If load-factor-increase-period-in-seconds is set and load-increase-factor is not set, the recovered instance gets no load for load-factor-increase-period-in-seconds. After load-factor-increase-period-in-seconds lapses, the load factor for the recovered instance becomes 1.

sendUDPResponseFromBackend

false

If true, specifies that UDP responses are sent to the client from the back end instead of the front end, saving an extra network hop.