Gluster users - Aug 2009 - Server side mount point confusion

If you have an AFR server and a process on the server writes or reads 
directly from the server's mount point (not using a glusterfs client 
connection) how does that affect replication?

I'm trying out a simple test environment at the moment and I setup a 1 
server and 1 client on the same computer. I touched a file from the 
glusterfs client mount point and noted it appeared in the normal server 
mount point. Then I touched a file on the server mount point and it 
appeared on the client, but since I do not have another computer to test 
with I'm not sure if this second test would have been replicated 
correctly, or if doing this negatively affects the system. If so is 
there a good way to help to avoid this type of direct access?

My goal is to have simple fail-over with 2 servers replicating data 
between themselves with apache on each one serving files only from their 
local copy of the glusterd data. I'm assuming the apache configuration 
has to use the local client mount point for its document root.

Any pointers for such a setup are much appreciated.

Justin Kolb wrote:
> If you have an AFR server and a process on the server writes or reads 
> directly from the server's mount point (not using a glusterfs client 
> connection) how does that affect replication?
Interacting with the ? raw ? data is a generally a no-no.  Interactions 
should be done via the client or else they will not be reflected on any 
other members of the storage group.
> correctly, or if doing this negatively affects the system. If so is 
> there a good way to help to avoid this type of direct access?
There's nothing stopping you from running both a client and a server 
process on a given machine.  It's the same binary - just a different 
invocation.



--
dan.