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 2nd 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. -Tony --------------------------- Manager, IT Operations Format Dynamics, Inc. P: 303-228-7327 F: 303-228-7305 [email protected] http://www.formatdynamics.com <http://www.formatdynamics.com/> From: [email protected] [mailto:[email protected]] On Behalf Of paul simpson Sent: Wednesday, May 18, 2011 8:05 AM To: Whit Blauvelt Cc: [email protected] Subject: Re: [Gluster-users] gluster 3.2.0 - totally broken? hi guys, we're using 3.1.3 and i'm not moving off it. i totally agree with stephans comments: the gluster devs *need* to concentrate on stability before adding any new features. it seems gluster dev is sales driven - not tech focused. we need less new buzz words - and more solid foundations. gluster is a great idea - but is in danger of falling short and failing if the current trajectory is now altered. greater posix compatibility (permissions, NLM locking) should be a perquisite for an NFS server. hell, the documentation is terrible; it's hard for us users to contribute to the community when we are groping around in the dark too. question : is anyone using 3.2 in a real world production situation? regards to all, -paul On 18 May 2011 14:54, Whit Blauvelt <[email protected]> wrote: >From reading this list, I wonder if this would be an accurate summary of the current state of Gluster: 3.1.3 - most dependable current version 3.1.4 - gained a few bugs 3.2.0 - not stable So 3.1.3 would be suitable for production systems, as long as the known bug in mishandling Posix group permissions is worked around (by loosening permissions). There has been a suggestion that stat-prefetch be turned off, and perhaps that other, non-default options are better not used. Now, I'm not personally knowledgeable on any of this aside from the Posix group problem. Just asking for confirmation or not of the basic sense I'm getting from those with extensive experience that 3.1.3 is essentially dependable, while 3.1.4 is problematic, and 3.2.0 should perhaps only be used if you want to gain familiarity with the new geo-replication feature, but avoided for current production use. Whit _______________________________________________ Gluster-users mailing list [email protected] http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list [email protected] http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
