Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!hpfcso!hpfcdc!rml
From: rml@hpfcdc.HP.COM (Bob Lenk)
Newsgroups: comp.sys.hp
Subject: Re: why do cluster clients panic after cluster servers die
Message-ID: <5570431@hpfcdc.HP.COM>
Date: 7 Jun 90 19:56:42 GMT
References: <1720008@hpbbi4.HP.COM>
Organization: HP Ft. Collins, Co.
Lines: 21

In article <CPH.90Jun1021135@kleph.ai.mit.edu> cph@zurich.ai.mit.edu (Chris Hanson) writes:

> It seems to me that the diskless protocol could be extended in an
> upwards-compatible way so that the client supplied the necessary
> information to the server to permit resynchronization when the server
> had lost the information for one reason or another.  Certainly the
> client knows all of the relevant state, such as what files are open.

The relevant information can include things the client doesn't keep
track of, such as what data was in the server's buffer cache and what
the layout of the server's swap space was.

> A little cleverness in the design of this software could eliminate a
> lot of headaches for customers.

I think it's possible to address this, (as well as making sense of the
information the client does have) but it would take significant effort.

		Bob Lenk
		rml@hpfcla.hp.com
		hplabs!hpfcla!rml