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
Gluster-users at gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
=20
------_=_NextPart_001_01CC157C.7ABF71FF
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-microsoft-com:office:office"
xmlns:w=3D"urn:schemas-microsoft-com:office:word"
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta
http-equiv=3DContent-Type content=3D"text/html;
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft
Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body
lang=3DEN-US link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p
class=3DMsoNormal><span
style=3D''font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D''>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.<o:p></o:p></span></p><p
class=3DMsoNormal><span
style=3D''font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D''>I
2<sup>nd</sup> 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.<o:p></o:p></span></p><p
class=3DMsoNormal><span
style=3D''font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D''><o:p> </o:p></span></p><p
class=3DMsoNormal><span
style=3D''font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D''>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.<o:p></o:p></span></p><p
class=3DMsoNormal><span
style=3D''font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D''><o:p> </o:p></span></p><p
class=3DMsoNormal><span
style=3D''font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D''>-Tony<o:p></o:p></span></p><p
class=3DMsoNormal><span
style=3D''font-size:10.0pt;font-family:"Courier
New";color:#1F497D''>---------------------------<o:p></o:p></span></p><p
class=3DMsoNormal><span
style=3D''font-size:10.0pt;font-family:"Courier
New";color:#1F497D''>Manager, IT
Operations<o:p></o:p></span></p><p
class=3DMsoNormal><span
style=3D''font-size:10.0pt;font-family:"Courier
New";color:#1F497D''>Format Dynamics,
Inc.<o:p></o:p></span></p><p
class=3DMsoNormal><span
style=3D''font-size:10.0pt;font-family:"Courier
New";color:#1F497D''>P:
303-228-7327<o:p></o:p></span></p><p
class=3DMsoNormal><span
style=3D''font-size:10.0pt;font-family:"Courier
New";color:#1F497D''>F:
303-228-7305<o:p></o:p></span></p><p
class=3DMsoNormal><span
style=3D''font-size:10.0pt;font-family:"Courier
New";color:#1F497D''><a href=3D"mailto:abiacco at
formatdynamics.com">abiacco at
formatdynamics.com</a><o:p></o:p></span></p><p
class=3DMsoNormal><span
style=3D''font-size:10.0pt;font-family:"Courier
New";color:#1F497D''><a
href=3D"http://www.formatdynamics.com/">http://www.formatdynamics.com</a><o:p></o:p></span></p><p
class=3DMsoNormal><span
style=3D''font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D''><o:p> </o:p></span></p><div
style=3D''border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in
4.0pt''><div><div
style=3D''border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in
0in 0in''><p class=3DMsoNormal><b><span
style=3D''font-size:10.0pt;font-family:"Tahoma","sans-serif"''>From:</span></b><span
style=3D''font-size:10.0pt;font-family:"Tahoma","sans-serif"''>
gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at
gluster.org] <b>On Behalf Of </b>paul
simpson<br><b>Sent:</b> Wednesday, May 18, 2011 8:05
AM<br><b>To:</b> Whit Blauvelt<br><b>Cc:</b>
gluster-users at gluster.org<br><b>Subject:</b> Re:
[Gluster-users] gluster 3.2.0 - totally
broken?<o:p></o:p></span></p></div></div><p
class=3DMsoNormal><o:p> </o:p></p><p
class=3DMsoNormal>hi guys,<o:p></o:p></p><div><p
class=3DMsoNormal><o:p> </o:p></p></div><div><p
class=3DMsoNormal>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.
<o:p></o:p></p></div><div><p
class=3DMsoNormal><o:p> </o:p></p></div><div><p
class=3DMsoNormal>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.<o:p></o:p></p></div><div><p
class=3DMsoNormal><o:p> </o:p></p></div><div><p
class=3DMsoNormal>question : is anyone using 3.2 in a real world production
situation?<o:p></o:p></p></div><div><p
class=3DMsoNormal><o:p> </o:p></p></div><div><p
class=3DMsoNormal>regards to
all,<o:p></o:p></p></div><div><p
class=3DMsoNormal><o:p> </o:p></p></div><div><p
class=3DMsoNormal>-paul<o:p></o:p></p></div><div><p
class=3DMsoNormal
style=3D''margin-bottom:12.0pt''><o:p> </o:p></p><div><p
class=3DMsoNormal>On 18 May 2011 14:54, Whit Blauvelt <<a
href=3D"mailto:whit.gluster at transpect.com">whit.gluster at
transpect.com</a>> wrote:<o:p></o:p></p><p
class=3DMsoNormal>From reading this list, I wonder if this would be an
accurate summary of the<br>current state of
Gluster:<br><br>3.1.3 - most dependable current
version<br><br>3.1.4 - gained a few bugs<br><br>3.2.0 -
not stable<br><br>So 3.1.3 would be suitable for production systems,
as long as the known bug<br>in mishandling Posix group permissions is
worked around (by loosening<br>permissions).<br><br>There has
been a suggestion that stat-prefetch be turned off, and perhaps<br>that
other, non-default options are better not used.<br><br>Now,
I''m not personally knowledgeable on any of this aside from the
Posix<br>group problem. Just asking for confirmation or not of the basic
sense I''m<br>getting from those with extensive experience that
3.1.3 is essentially<br>dependable, while 3.1.4 is problematic, and 3.2.0
should perhaps only be<br>used if you want to gain familiarity with the
new geo-replication feature,<br>but avoided for current production
use.<br><span
style=3D''color:#888888''><br>Whit</span><o:p></o:p></p><div><div><p
class=3DMsoNormal>_______________________________________________<br>Gluster-users
mailing list<br><a href=3D"mailto:Gluster-users at
gluster.org">Gluster-users at gluster.org</a><br><a
href=3D"http://gluster.org/cgi-bin/mailman/listinfo/gluster-users"
target=3D"_blank">http://gluster.org/cgi-bin/mailman/listinfo/gluster-users</a><o:p></o:p></p></div></div></div><p
class=3DMsoNormal><o:p> </o:p></p></div></div></div></body></html>
------_=_NextPart_001_01CC157C.7ABF71FF--