I'm fairly confident that the docs are talking about this: 1) it's not recommended to have replicated bricks accross long distances (am not from US so I don't know the exact distance between Seattle and Chapel Hill, but it sounds far haha) 2) would geo-replication be the way to go? Anybody correct me if this is not so! ..maybe give the docs one more go? v On Wed 19 Mar 2014 12:06:37, Cary Tsai wrote: > Hi There: > New to the GlusterFS and could not find the answer from the document > so hope I can get the answer form the mailing list. > > Let's say we have two web servers: > One in Seattle, WA and another one is in Chapel Hill, NC. > So I create a 'replicated' volume which one brick in WA and another brick > in NC. > I assume the web server in both WA and NC can mount the 'replicated' volume. > There are 2 HTTP/Get calls from CA and NY. > We assume CA's HTTP/Get is sent to web server in WA and > NY's HTTP/Get is sent to web server in NC. > > My question is does the web server in WA definitely gets the data > from the brick in WA? If not, is any way to configure so the > web server in WA definitely gets data from the brick in WA? > > Thanks > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://supercolony.gluster.org/mailman/listinfo/gluster-users -- Regards Viktor Villafuerte Optus Internet Engineering t: 02 808-25265 _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
