Thanks, done.
Also, I noticed that even when you successfully create a volume and then delete
it, it still leaves the extended attributes on the directories. Is this by
design or should I report this as a bug (seems like a bug to me!).
Jeff
On Aug 9, 2012, at 6:58 PM, Joe Julian wrote:
On
Hello
What am I doing wrong?!?
I have a test setup with 4 identical servers with 2 disks each in
distribute-replicate 2. All servers are connected to a GB switch.
I am experiencing really slow speeds at anything I do. Slow write, slow
read, not to mention random write/reads.
Here is an
So I stopped a node to check the BIOS and after it went up, the
rebalance kicked in. I was looking for those kind of speeds on a normal
write. The rebalance is much faster than my rsync/cp.
https://dl.dropbox.com/u/282332/Screen%20Shot%202012-08-10%20at%202.04.09%20PM.png
Best Regards
Ivan
Hi Ivan,
that's because Gluster has really bad many small files performance
due to it's architecture.
On all stat() calls (which rsync is doing plenty of), all replicas are
being checked for integrity.
regards,
Philip
2012/8/10 Ivan Dimitrov dob...@amln.net:
So I stopped a node to check the
On Fri, Aug 10, 2012 at 11:12:54AM +0200, Jeff Williams wrote:
Also, I noticed that even when you successfully create a volume and then
delete it, it still leaves the extended attributes on the directories. Is
this by design or should I report this as a bug (seems like a bug to me!).
running 3.3 distributed on IPoIB on 4 nodes, 1 brick per node. Any idea
why, on one of those nodes, glusterfsd would go berserk, running up to 370%
CPU and driving load to 30 (file performance on the clients slows to a
crawl). While very slow, it continued to serve out files. This is the
second
