Date: Mon, 05 Apr 2010 16:43:06 -0400 From: jfarmer@goldsword.com To: freebsd-stable@freebsd.org Subject: Re: fault tolerant web servers on freebsd Message-ID: <20100405164306.hmy4n8pvs4goc8ks@www.goldsword.com> In-Reply-To: <4BBA4478.7030302@gausus.net> References: <1209800810.33861270466947931.JavaMail.root@dagobah.intersec.pl> <4BBA05A2.40706@intertainservices.com> <4BBA1823.1090305@gausus.net> <4BBA4334.1020506@interazioni.it> <4BBA4478.7030302@gausus.net>
index | next in thread | previous in thread | raw e-mail
Quoting Maciej Jan Broniarz <gausus@gausus.net>:
> W dniu 10-04-05 22:08, Tonix (Antonio Nati) pisze:
>> Maciej Jan Broniarz ha scritto:
>>> W dniu 10-04-05 17:45, Mike Jakubik pisze:
>>
>> Just to use exact words, fault toulerancy is not possible with any
>> FreeBSD/Linux O.S.
>> F.T. means outage can occur in every moment, but all current operation
>> will be always completed by other equipments; so there will not be
>> interrupted/lost operations.
>
> Hmm. Thanks for the tip. Which *NIX os can be used to build an FT
> solution then? Solaris? AIX? HP-UX?
You're asking a question that has not easy or compete answer. Fault
tolerant at what level? Do you want to guarantee that _every_ DB
operation competes? What about random file reads or writes? Do you
want to guarantee that two identical operations with the same data
will produce the same result? (That's _not_ the same as the previous
questions...)
So first you have to define your workload, then define what errors you
must avoid or allow, and then define how to deal with failures,
errors, etc.
Then you can start talking about High Availability vs. level of Fault
tolerance, vs. ....
John
-----------------------------------------------------------------
J. T. Farmer <jfarmer@goldsword.com> <jfarmer@orfencer.org>
GoldSword Systems, Knoxville TN Coach & Instructor
Consulting, Knoxville Academy of the Blade
Software Development, Maryville Fencing Club
Project Management
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100405164306.hmy4n8pvs4goc8ks>