From owner-freebsd-hackers Wed Mar 4 10:09:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14231 for freebsd-hackers-outgoing; Wed, 4 Mar 1998 10:09:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA14063 for ; Wed, 4 Mar 1998 10:09:11 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yAII3-000329-00; Wed, 4 Mar 1998 09:49:11 -0800 Date: Wed, 4 Mar 1998 09:48:50 -0800 (PST) From: Tom To: Niall Smart cc: "Ron G. Minnich" , Alex Povolotsky , hackers@FreeBSD.ORG Subject: Re: Cluster? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 4 Mar 1998, Niall Smart wrote: > I think a good approach to transparent clustering is through distributed > shared memory. However, the coherencey schemes used for high reliability Or via a distributed lock manager, and shared disk storage. I understand this is how current cluster development is going. > of months from now though. One particular thing that could benefit > easily from this are DNS servers, other servers like mail and news wouldn't DNS? DNS already has excellent fault-tolerant capabilities. > be so easy, because of the need for a reliable shared filesystem. Plus > there is the problem of how to get clients of these servers to contact > the redundant one in the event of a failure, I think someone has done > something in this area using proxy arp... This is the important bit. IP address assumption is critical. Some clusters do it by assuming the MAC address to ensure an instant transition. > Niall Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message