* Jorj Bauer <[EMAIL PROTECTED]> [2008-10-23 20:08]: > A question for anyone running production cosignd/authN servers with > multiple replicating hosts using a round-robin: how do you handle > failures? > > For example: do you have documented procedures for your staff to > immediately remove down hosts from the round-robin, or do you weather > the potential outage? > > Other advice for redundant configuration and best uptime?
You might skim through this page on the Shibboleth IdP, ignoring the bits about Java and state being in memory, the rest still applies: https://spaces.internet2.edu/display/SHIB2/IdPClusterIntro In short: DNS round robin is load distribution (at best) and provides nothing for failover or high availability. Cheers, -peter -- [EMAIL PROTECTED] - vienna university computer center Universitaetsstrasse 7, A-1010 Wien, Austria/Europe Tel. +43-1-4277-14155, Fax. +43-1-4277-9140 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Cosign-discuss mailing list Cosign-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cosign-discuss
