<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 14, 2016 at 8:24 PM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Mon, Nov 14, 2016 at 04:50:44PM +0530, Pranith Kumar Karampuri wrote:<br>
> On Mon, Nov 14, 2016 at 4:38 PM, Gandalf Corvotempesta <<br>
> <a href="mailto:gandalf.corvotempesta@gmail.com">gandalf.corvotempesta@gmail.<wbr>com</a>> wrote:<br>
><br>
> > 2016-11-14 11:50 GMT+01:00 Pranith Kumar Karampuri <<a href="mailto:pkarampu@redhat.com">pkarampu@redhat.com</a>>:<br>
> > > To make gluster stable for VM images we had to add all these new features<br>
> > > and then fix all the bugs Lindsay/Kevin reported. We just fixed a<br>
> > corruption<br>
> > > issue that can happen with replace-brick which will be available in 3.9.0<br>
> > > and 3.8.6. The only 2 other known issues that can lead to corruptions are<br>
> > > add-brick and the bug you filed Gandalf. Krutika just 5 minutes back saw<br>
> > > something that could possibly lead to the corruption for the add-brick<br>
> > bug.<br>
> > > Is that really the Root cause? We are not sure yet, we need more time.<br>
> > > Without Lindsay/Kevin/David Gossage's support this workload would have<br>
> > been<br>
> > > in much worse condition. These bugs are not easy to re-create thus not<br>
> > easy<br>
> > > to fix. At least that has been Krutika's experience.<br>
> ><br>
> > Ok, but this changes should be placed in a "test" version and not<br>
> > marked as stable.<br>
> > I don't see any development release, only stable releases here.<br>
> > Do you want all features ? Try the "beta/rc/unstable/alpha/dev" version.<br>
> > Do you want the stable version without known bugs but slow on VMs<br>
> > workload? Use the "-stable" version.<br>
> ><br>
> > If you relase as stable, users tend to upgrade their cluster and use<br>
> > the newer feature (that you are marking as stable).<br>
> > What If I upgrade a production cluster to a stable version and try to<br>
> > add-brick that lead to data corruption ?<br>
> > I have to restore terabytes worth of data? Gluster is made for<br>
> > scale-out, what I my cluster was made with 500TB of VMs ?<br>
> > Try to restore 500TB from a backup....................<br>
> ><br>
> > This is unacceptable. add-brick/replace-brick should be common "daily"<br>
> > operations. You should heavy check these for regression or bug.<br>
> ><br>
><br>
> This is a very good point. Adding other maintainers.<br></div></div></blockquote><div><br></div><div>I think Pranith's intention here was to bring to other maintainers' attention the point about<br></div><div>development releases vs stable releases although his inline comment may have been a<br></div><div>bit out-of-place (I was part of the discussion that took place before this reply of his, in office<br>today, hence taking the liberty to clarify).<br></div><div><br></div><div>-Krutika<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
<br>
</div></div>Obviously this is unacceptible for versions that have sharding as a<br>
functional (not experimental) feature. All supported features are<br>
expected to function without major problems (like corruption) for all<br>
standard Gluster operations. Add-brick/replace-brick are surely such<br>
Gluster operations.<br>
<br>
Of course it is possible that this does not always happen, and our tests<br>
did not catch the problem. In that case, we really need to have a bug<br>
report with all the details, and preferably a script that can be used to<br>
reproduce and detect the failure.<br>
<br>
FWIW sharding has several open bugs (like any other component), but it<br>
is not immediately clear to me if the problem reported in this email is<br>
in Bugzilla yet. These are the bugs that are expected to get fixed in<br>
upcoming minor releases:<br>
<a href="https://bugzilla.redhat.com/buglist.cgi?component=sharding&f1=bug_status&f2=version&o1=notequals&o2=notequals&product=GlusterFS&query_format=advanced&v1=CLOSED&v2=mainline" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>buglist.cgi?component=<wbr>sharding&f1=bug_status&f2=<wbr>version&o1=notequals&o2=<wbr>notequals&product=GlusterFS&<wbr>query_format=advanced&v1=<wbr>CLOSED&v2=mainline</a><br>
<br>
HTH,<br>
Niels<br>
<br>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br></blockquote></div><br></div></div>