Coda File System

Re: Coda deployment

From: Ivan Popov <>
Date: Wed, 11 Jun 2003 18:45:30 +0200 (MET DST)
On Wed, 11 Jun 2003, Jan Harkes wrote:

> > the expected behaviour is that the clients contact the server that they
> > assume to be more responsive - based on their checks.
> > That is, the choice is dynamic, and depends not only on the net topology.
> > Should be fine in your case, anyway.

> The actual file fetches occur from the server they think they have the
> best connection to. But attribute information, stores, etc. go to both
> servers. Until.... a client decides that one or more members in the
> replication group are slow. Then the client switches to weakly-connected

Aargh. Thanks Jan for correcting me!

Of course, it is "mostly read-only" data that suits well to be put on
geographically distinct servers.
Updates in strongly connected mode would not create extra overhead, but
the speed then is limited by the slowest client-server link.

So, data being heavily updated is more efficiently kept in one place
(possibly replicated, but replicated "within good connectivity").

Received on 2003-06-11 12:48:19