OK, I finally had some time to read through the
code.
The difference between auth.props
enableLoadBalancing=false and utadm -f is subtle:
auth.props enableLoadBalancing=false
- Checked only locally during startup
- Information not propagated within group
- Causes any DTUs which connect locally
to not get redirected to other hosts for
load balancing (but they will still get
redirected if there's an existing session
for the token someplace in the group)
utadm -f
- Checked periodically (no need for restart)
- Information propagated throughout group
(and visible via utgstatus)
- Causes *other* hosts in group to not direct DTUs to
this server for load balancing, and this
server to direct DTUs away unless they have a
local session for the token already
For practical purposes, if you set the same
setting everywhere in the group and restart SRSS
these will have the same effect.
utadm -f is preferred:
- no restart required after configuration change
- possible to make only part of the group decline
participation in load balancing (e.g. standby
failover servers, or to cause them to stop
taking new sessions in anticipation of a
planned upcoming outage for upgrade or
similar)
If you set auth.props enableLoadBalancing=false
for only *some* of the servers, you'll get
inconsistent and unpredictable behavior. It
should be used for 'none' or 'all' servers, never
for only 'some' (at least at the moment I can't
think of a way to get useful behavior by doing
this, maybe there's a highly unusual scenario
where it might be useful).
-Bob
Christopher Saul wrote:
According to the docs you can set -
enableLoadBalancing = false
in auth.props
Maybe you're not as old as you thought? :)
Craig Bender wrote:
Hi Bob,
That's not what I meant, but It's a great suggestion considering I'm
not even sure what I meant regarding the load balancing now.
I swore there was a setting in auth.props to turn off load balancing,
but turns out there is not. Chalk that one up to a random access
memory failure. The mileage is starting to show... :(
Bob Doolittle wrote:
Wolfgang Engelien wrote:
From: Craig Bender <[EMAIL PROTECTED]>
If you don't have a failover group, then one server will not know
about
the other, including sessions.
What about:
Disabling load balancing and turning on select at login in
auth.props?
Yes, this seems to be exactly what I need. Thanks Craig.
Can I do the change while the servers are running and then do a
soft reset or is a restart necessary with all sessions terminated?
The "select at login" piece is automatic, no
restart required - just edit auth.props and it will
pick it up immediately. By the "disable load
balancing" I think Craig means "utadm -f" and I
can't recall whether that requires a soft reset or
not. Definitely no need to terminate sessions with
a -c hard reset.
-Bob
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
