I understand that.
Our application basically is one brick is doing write and others read.
And even 'write' is batch write. Not like the regular FS operations.
The data written to the mirror volume is very low.
The entire volume is 8GB (SSD) and only on average 50 MBs per day that kind of traffic.
Cary
On Mon, May 5, 2014 at 2:16 PM, James <purpleidea@xxxxxxxxx> wrote:
On Mon, May 5, 2014 at 5:11 PM, Cary Tsai <f4lens@xxxxxxxxx> wrote:BTW, normal gluster mode isn't usually meant for "geo-distribution"...
> I have 4 systems, us-east-1, us-east-2, us-west-1, and us-west-2.
> From us-east-1, it sees us-east-2 state as : Accepted peer request
> (Connected)
> But other systems sees it as "Peer in Cluster (Connected)"
>
> Due to us-east-2 is " Accepted peer request " I cannot create a volume
> using brick in us-east-2 on us-east-1.
>
> How do I make us-east-2 seen as "Peer in Cluster" in us-east-1?
>
> Thanks
You might want to look at the geo-replication feature instead.
HTH
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
