Re: [PATCH / RFC] nfs-utils: High Availability NFS

[Kedar Sovani <kedars@hotpop.com>]

On Mon, 2004-09-06 at 07:17, Neil Brown wrote:
> On  September 3, kedars@hotpop.com wrote:
> > NFS Server keeps state about the recent responses given to the clients,
> > in a reply cache.
> > 
> > Shouldn't that state be replicated to the failed-over NFS server as well
> > ?
> 
> The reply cache is an optimisation and cannot be relied upon.  Coping
> it across in a fail-over would be both very expensive (it is highly
> volatile) and of little benefit.
> 
> NeilBrown

Yes, migrating it across server would be very expensive.

But isn't reply cache for correctness (idempotency) as against
optimisation ? 
E.g. 
1. NFS Client sends "create" (file) to the server.
2. Server creates the file and sends a "success" response.
3. The response is lost.
4. The Client retries the "create" 
5. and the NFS Server responds from the _reply cache_ stating that the
result is true. (as the reply was cached in step 2)

Now if the Server crashes after the 3rd step, and the failed over server
starts processing requests, it will respond to the step 4 above with a
FILE EXISTS instead of success, which I think, is incorrect.

Am I missing something ? 
Or probably such scenarios are rare to occur and if they do, are not
much significant, I suppose.

I guess this is what you meant by "of little benefit" above.

thanks,
Kedar.




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs