Thank you.
I will try geo ..
On 22/10/12 16.44, Joe Julian wrote:
On 10/22/2012 07:37 AM, Joe Julian wrote:
The native Gluster client tends to be really @#$@#$@# stupid. It'll
send reads to Singapore while you're in Virginia (and there are
bricks 0.2ms away),
False. The client will read from
On 10/22/2012 10:37 AM, Joe Julian wrote:
> The client will read from the first-to-respond.
That's true, but it's going to change in a couple of ways.
* Commit 0baa12e8 (March 23) will cause replication to read from a brick on the
same machine if there is one.
* Commit 97819bf2 (June 24) provide
- Original Message -
> > False. The client will read from the first-to-respond. Yes, if
> > Singapore is responding faster than Virginia you might want to
> > figure
> > out why Virginia is so overloaded that it's taking more than 200ms
> > to
> > respond, but really that shouldn't be the
On 10/22/2012 07:37 AM, Joe Julian wrote:
The native Gluster client tends to be really @#$@#$@# stupid. It'll
send reads to Singapore while you're in Virginia (and there are
bricks 0.2ms away),
False. The client will read from the first-to-respond. Yes, if
Singapore is responding faster than V
On 10/21/2012 02:18 PM, Israel Shirk wrote:
Haris, try the NFS mount. Gluster typically triggers healing through
the client, so if you skip the client, nothing heals.
Not true anymore. With 3.3 there's a self-heal daemon that will handle
the heals. You do risk reading stale data if you don't re
Thank you for your answer...
Does using the NFS client insure replication to all bricks? My problem
is that I see Gluster has "unfinished" replication tasks that lie
around. Seems like the Gluster needs an external trigger to like "ls -l"
on the file in question to re-trigger and complete the r
Haris, try the NFS mount. Gluster typically triggers healing through the
client, so if you skip the client, nothing heals.
The native Gluster client tends to be really @#$@#$@# stupid. It'll send
reads to Singapore while you're in Virginia (and there are bricks 0.2ms
away), then when healing is
On Sat, Oct 20, 2012 at 08:33:46AM +0200, Haris Zukanovic wrote:
> My problem is that files sometimes do not replicate to all 3 servers
> instantly. There are certainly short network outages which may
> prevent instant replication and I have situations like this:
The CAP theorem says that out of C
Hi everyone,
I am using Gluster in replication mode.
Have 3 bricks on 3 different physical servers connected with WAN. This
makes writing but also reading files from Gluster mounted volume very slow.
To remedy this I have made my web application read Gluster files from
the brick directly (I mak
