On Thu, 2007-07-19 at 11:29 +0100, lists wrote:
> So are their any problems caused by setting both expire_nodest_conn and
> expire_quiescent_template?
None that I can think of directly; however if a healthcheck fails
because something goes awry (local intervening network conditions,
transient load on director, something like that) then a realserver could
well be quiescent or removed briefly - in which case all established
persistent sessions will be terminated. This may not be desirable in the
case of a condition which is resolved in a few seconds.
I guess careful tuning of healthchecks along with good network design
would be the way to not trigger it, but that's outside the scope of this
discussion :)
> They would seem to be logical defaults in most situations?
> Unless for some strange reason you don't want users to swap real server
> when it is down or in maintenance mode?
Well, see the above hypothetical situations - where that happens, the
sessions will simply continue if the sysctls were unset.
Graeme
|