I had issues with hanging of mounts as well with 3.2. I fixed it via upping
the number of connections allowed to the fuse mount... by default it's
something silly low like 16. I don't quite understand why the basic options
are not at least slightly optimized for more than a few connections. Try
this and see if it helps with 3.2. It helped me, but this is also a 3.1.x
fix as well...
Edit: /etc/glusterd/vols/<volname>/<volname>-fuse.vol
<Replicate and brick entries above here>
volume <volname>-write-behind
type performance/write-behind
option cache-size 4MB
option flush-behind on
subvolumes <volname>-replicate-0
end-volume
volume <volname>-read-ahead
type performance/read-ahead
option page-count 4
subvolumes <volname>-write-behind
end-volume
volume <volname>-io-cache
type performance/io-cache
option cache-size 768MB
option cache-timeout 1
subvolumes <volname>-read-ahead
end-volume
volume <volname>-quick-read
type performance/quick-read
option cache-timeout 1
option cache-size 768MB
option max-file-size 64kB
subvolumes <volname>-io-cache
end-volume
#volume sitestore-stat-prefetch
# type performance/stat-prefetch
# subvolumes <volname>-quick-read
#end-volume
volume <volname>
type debug/io-stats
option latency-measurement off
option count-fop-hits off
# subvolumes <volname>-stat-prefetch
subvolumes <volname>-quick-read
end-volume
Justice London
PLEASE NOTE: This message, including any attachments, may include
privileged, confidential and/or inside information. Any distribution or use
of this communication by anyone other than the intended recipient(s) is
strictly prohibited and may be unlawful. If you are not the intended
recipient, please notify the sender by replying to this message and then
delete it from your system.
-----Original Message-----
From: gluster-users-bounces at gluster.org
[mailto:gluster-users-bounces at gluster.org] On Behalf Of Tomasz Chmielewski
Sent: Wednesday, May 18, 2011 10:05 AM
To: Anthony J. Biacco
Cc: gluster-users at gluster.org
Subject: Re: gluster 3.2.0 - totally broken?
On 18.05.2011 18:56, Anthony J. Biacco wrote:
> I'm using it in real-world production, lot of small files (apache
> webroot mounts mostly). I've seen a bunch of split-brain and self-heal
> failing when I first did the switch. After I removed and recreated the
> dirs it seemed to be fine for about a week now; yeah not long, I know.
>
> I 2^nd the notion that it'd be nice to see a list of what files/dirs
> gluster thinks is out of sync or can't heal. Right now you gotta go
> diving into the logs.
>
> I'm actually thinking of downgrading to 3.1.3 from 3.2.0. Wonder if I'd
> have any ill-effects on the volume with a simple rpm downgrade and
> daemon restart.
I've been using 3.2.0 for a while, but I had a problem with userspace
programs "hanging" on accessing some files on the gluster mount
(described here on the list).
I downgraded to 3.1.4 (remove 3.2.0 rpm and config, install 3.1.4 rpm,
add nodes) and it works fine for me.
3.0.x was also crashing for me when SSHFS-like mount was used to the
server with gluster mount (and reads/writes were made from the gluster
mount through it).
--
Tomasz Chmielewski
http://wpkg.org
_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
