Gluster users - Sep 2009 - How does replication work?

Like the subject implies, how does replication work exactly?

If a client is the only one that has the IP addresses defined for the servers,
does that mean that only a client writing a file ensures that it goes to both
servers? That would tell me that the servers don't directly communicate with
each other for replication.

If so, how does healing work? Since the client is the only configuration with
the multiple server IP addresses, is it the client's "task" to
make sure the server heals itself once it's back online?

If not, how do they servers know each other exist if not for the client config
file?

Alan Ivey wrote:
> Like the subject implies, how does replication work exactly?
> 
> If a client is the only one that has the IP addresses defined for the
servers, does that mean that only a client writing a file ensures that it goes
to both servers? That would tell me that the servers don't directly
communicate with each other for replication.
> 
> If so, how does healing work? Since the client is the only configuration
with the multiple server IP addresses, is it the client's "task"
to make sure the server heals itself once it's back online?
> 
> If not, how do they servers know each other exist if not for the client
config file?
You've answered your own question. :)  AFAIK, in the recommended simple 
replication scenario, the client is actually responsible for 
replication, as each server is functionally independant.

(This seems crazy to me, but yes, that's how it works.)


-- 
Daniel Maher <dma+gluster at witbe.net>