<font color="#000000"><font size="2"><font face="verdana,sans-serif"><div>Kind of bizzare I have to agree, but as far as I can understand from the docs geo-replication is one way, and I need two way because there can be writes on both sides, rsync was an option but I would have to cron it and each side at a time, and from my understanding could give me problems of files either going missing or not being deleted.</div>
<div>Using the local for read is an option but since the files are being read and written by the same application (apache) I see no way to split that.</div><div>What is more weird is that I managed to get it to read just one side for a moment, after restarting gluster because of some adjustments, it started reading both nodes again, even restoring config backups had no effect.</div>
<div> </div><div></div></font><div></div></font><div></div></font><div>
On Tue, Sep 27, 2011 at 1:37 PM, Whit Blauvelt <span dir="ltr"><<a href="mailto:whit@transpect.com">whit@transpect.com</a>></span> wrote:<br></div><div class="gmail_quote"><blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;" class="gmail_quote">
Okay, what you're doing is a bizarre use of Gluster anyway. (They'd say you<br>
should use the "georeplication" instead - at which point a rsync run from<br>
cron will get you to about the same place without using Gluster at all.) But<br>
you can have local systems read from the backing store without corrupting<br>
the Gluster mirroring. Your writes all have to go through the Gluster<br>
mounts, but your reads don't.<br>
<font color="#888888"><br>
Whit<br>
</font><div><div></div><div class="h5"><br>
On Tue, Sep 27, 2011 at 01:22:24PM +0100, Lone Wolf wrote:<br>
> Just checked it is mounted with noatime<br>
><br>
> No dia 27 de Set de 2011 12:56, "Whit Blauvelt" <<a href="mailto:whit.gluster@transpect.com">whit.gluster@transpect.com</a>><br>
> escreveu:<br>
> > On Tue, Sep 27, 2011 at 12:15:50PM +0100, Lone Wolf wrote:<br>
> ><br>
> >> So I am assuming gluster is distributing the reads, being created with the<br>
> >> CLI I tried to edit the configurations manually and added "option<br>
> >> read-subvolume volume_name" to the cluster/replicate volume, being the<br>
> >> read-subvolume the local one.<br>
> ><br>
> > Do you have your filesystems mounted "noatime"? If not, every read requires<br>
> > the atime (last access time) to be written to the files on both mirrors.<br>
> ><br>
> > Whit<br>
><br>
</div></div></blockquote></div><br>