Bob,
Thank you very much. This was very helpful!
Wolfgang
At 11:22 PM 4/10/2006 +0300, you wrote:
>> Chooser yes, load balancing change, no.
>
>
> Hm, that means that the chooser is working with the load balancing
> still active?! So, I guess the selectAtLogin is actually overriding
> the load balancing calculations and is therefor making it appear as if
> load balancing is turned off.
Correct. After a utselect ("chooser") or utswitch load balancing will
not occur.
However the session in which you are seeing the actual utselect has already
been load balanced.
>
>> Again I encourage you to use utadm -f instead.
>> That will also take immediate effect.
>
>
> I actually don't want to take any server offline; I just wanted to be
> able to select the server I want to logon to without the load
> balancing choosing for me.
That's exactly what 'utadm -f' does. "offline" is
frankly a misnomer. What it actually means is "do
not participate in load balancing". No other
hosts in the group will attempt to load balance to
the server, and the server itself will send DTUs
to an online server in the group (if there is one)
for load balancing. If all servers are "offline",
no load balancing occurs - exactly the same as
"enableLoadBalancing=false" (except it takes
effect immediately).
>
>> This morning, after speaking to the engineer who is
>> the author/expert of this area, he responded with the
>> following:
>>
>> >enableLoadBalancing=false essentially shuts off the group manager
>> >completely. You don't want to do that. It was mainly there as a way of
>> >backing out the feature early on in case of bugs.
>
>
> Well, I guess I have to turn this back on, otherwise changes in the
> SRS accounts are not updated accross the group anymore?!
No, that's misunderstanding the role of the Group
Manager (GM). The GM is a part of utauthd that is
responsible for session location and load
balancing within the group. Nothing to do with
replicating the administrative data such as the
SRSS card registrations (that's handled directly
by SRDS - utreplica/utpulld/utpushd). In any case
see my follow-up comment from this engineer, he
was wrong and it was just the Load Balancing
aspect of the GM that was disabled through this
property.
You don't have to do anything, but I would
recommend setting utadm -f everywhere and
restoring enableLoadBalancing. At minimum this
will reduce load slightly due to truly disabling
load balancing. In practice this may not be
measurable, however.
Regards,
Bob
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
