> > Brandon, > > who does the copy is decided where the AFR translator is loaded. if you > > have AFR loaded on the client side, then the client does the two writes. > you > > can also have AFR loaded on the server side, and handle server do the > > replication. Translators can be loaded anywhere (client or server, > anywhere > > in the graph). You need to think more on the lines on how you can > 'program > > glusterfs' rather than how to 'configure glusterfs'. > > Performance-wise, which is better? Or does it make sense one way vs. > the other based on number of clients? Depends, if the interconnect between server and client is precious, then have the servers replicate (load afr on server side) with replication happening on a seperate network. This is also good if you have servers interconnected with high speed networks like infiniband. If your servers are having just one network interface (no seperate network for replication), and your client apps are IO bound, then it does not matter where you load AFR; they all would give the same performance. avati -- If I traveled to the end of the rainbow As Dame Fortune did intend, Murphy would be there to tell me The pot's at the other end.
