s only
netting me one!!!
On 5/11/2015 3:30 AM, Brian Ericson wrote:
tl;dr -- geo-replication of ~200,000 CHANGELOG files is killing me...
Help!
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users
tl;dr -- geo-replication of ~200,000 CHANGELOG files is killing me... Help!
I have about 125G spread over just shy of 5000 files that I'm
replicating with
geo-replication to nodes around the world. The content is fairly stable and
probably hasn't changed at all since I initially established
.tmp symbolic link
deletion and put me right back into the faulty state?
On 10/16/2015 01:35 AM, Aravinda wrote:
Do you see any errors in Master logs?
(/var/log/glusterfs/geo-replication//*.log)
regards
Aravinda
On 10/15/2015 07:51 PM, Brian Ericson wrote:
Thanks!
As near as I can tell, the Gluster
r sometime. Also let us know the
Gluster Version you are using.
regards
Aravinda
http://aravindavk.in
On 10/15/2015 05:20 AM, Brian Ericson wrote:
Admittedly an odd case, but...
o I have simple a simple geo-replication setup: master -> slave.
o I've mounted the master's volume on the master host
Admittedly an odd case, but...
o I have simple a simple geo-replication setup: master -> slave.
o I've mounted the master's volume on the master host.
o I've also setup rsyncd server on the master:
[master-volume]
path = /mnt/master-volume
read only = false
o I now rsync
On 06/10/2015 07:15 AM, Jeff Darcy wrote:
In short, it would seem that either were I to use geo-repliciation,
whether recommended or not in this kind of usage, I'd need to own both
which volume to mount and what to do with writes when the client has
chosen to mount the slave.
True. Various
On 06/09/2015 09:21 AM, Ted Miller wrote:
On 6/8/2015 5:55 PM, Brian Ericson wrote:
Am I misunderstanding
cluster.read-subvolume/cluster.read-subvolume-index?
I have two regions, A and B with servers a and b in,
respectfully, each region. I have clients in both regions.
Intra-region
On 06/09/2015 11:10 AM, Jeff Darcy wrote:
So, maybe passing these options as a mount command doesn't work/is a
no-op, but what I don't understand is why -- given that there is no
measure by which glusterfs should ever conclude the replica in the
other region is ever faster than the replica in
On 06/09/2015 10:37 AM, Jeff Darcy wrote:
Am I misunderstanding cluster.read-subvolume/cluster.read-subvolume-index?
I have two regions, A and B with servers a and b in,
respectfully, each region. I have clients in both regions. Intra-region
communication is fast, but the pipe between the
Am I misunderstanding cluster.read-subvolume/cluster.read-subvolume-index?
I have two regions, A and B with servers a and b in,
respectfully, each region. I have clients in both regions. Intra-region
communication is fast, but the pipe between the regions is terrible.
I'd like to minimize
10 matches
Mail list logo