Christer Bernérus wrote:
On 31 jan 2008, at 19:07, Bob Doolittle wrote:
Hi,
A few questions inline:
Christer Bernérus wrote:
Hi.
Today I tried to form a server failover group out of three solitary
servers.
How? What actions did you perform?
I did a utreplica -p <secondary server list> on the primary server,
then a utreplica -s <primary server> on the scondary servers.
This cmmand complained about not finding a port and gave me the option
o continuing by answering a question about
which version was running on the primary. This was version 3.1.1
(Linux RHAS btw)
You don't mention running utgroupsig here, but you do below.
Did you run it?
These had active sessions on them. It didn't turn out too well,
leaving hordes of disconnected DTU's looking for their lost session,
but never being able to connect to them.
What does this mean, exactly? Were the disconnected DTUs
showing an icon of some sort? What number was displayed in the
lower-right corner?
I actually didn't see this myself. I got a report on the phone from
our servicedesk.
Then I checked using utsession -p and all connections were marked "D"
and just "D"
If you ran utgroupsig and give all servers the same signature,
this ought to have worked.
Yes, that was what I expected too. I thought I did give the same sig.
What happens if I didn't ?
People will get new sessions on whichever server they happen to connect to,
even if they have an existing session on some other server. It's not
really a FoG
unless the utgroupsig matches on all members. You can run utgstatus and
it can tell you if utgroupsig is setup properly.
There are really two separate functions that we call "FoG". One is data
replication, and that's controlled by utreplica. The other is the group
signature, which controls whether servers will participate in load balancing
and session location/redirection.
-Bob
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
